Databases
StackOverflow2013
Postsdbo
POBuilding a test support artifact with dependencies
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBuilding a test support artifact with dependencies
    primarykey
    data
    text
    <p>I've got a situation where my source has both tests and some test support code, along with the usual source code. I want to be able to publish both the source and the test support as separate artifacts (each with its own set of dependencies), but obviously not the test classes.</p> <p>My directory structure looks like this:</p> <pre><code>src/main/... src/test/... src/testsupport/... </code></pre> <p>I have some dependencies defined, as per usual:</p> <pre><code>dependencies { compile 'com.sun.jersey:jersey-core:1.17.1' ... more compile dependencies... testCompile 'com.google.code.gson:gson:2.1' ... more testCompile dependencies... } </code></pre> <p>I also need the test support sourceSet:</p> <pre><code>sourceSets { testSupport { java { srcDir 'src/testsupport/java' } resources { srcDir 'src/testsupport/resources' } compileClasspath += sourceSets.test.compileClasspath runtimeClasspath += sourceSets.test.runtimeClasspath } } </code></pre> <p>I have to add the test classpaths to the testSupport ones because the testsupport code has the same dependencies.</p> <p>Finally, to create my artifact, I have:</p> <pre><code>task createTestSupportArtifact (type: Jar) { classifier = 'testsupport' from sourceSets.testSupport.output } artifacts { archives file: createTestSupportArtifact.archivePath, builtBy: createTestSupportArtifact } </code></pre> <p>However, in my other repository that depends on these artifacts, it's not pulling in any dependencies for the testsupport artifact. I have a few theories as to why (it doesn't have it's own POM or it doesn't know the scope is test at runtime), but nothing concrete.</p> <p>Is there a better approach to this? Perhaps using <code>configurations</code> intelligently?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDepressio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload