Databases
StackOverflow2013
Postsdbo
POExclude Test Classes in dependend Maven JAR
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExclude Test Classes in dependend Maven JAR
    primarykey
    data
    text
    <p>We have an EAR Project which assembles a WAR File and has some JAR Files as dependency. POM.xml of the EAR looks like this:</p> <pre><code>&lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;our.package&lt;/groupId&gt; &lt;artifactId&gt;package-impl&lt;/artifactId&gt; &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt; &lt;type&gt;jar&lt;/type&gt; &lt;scope&gt;runtime&lt;/scope&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-ear-plugin&lt;/artifactId&gt; &lt;version&gt;${maven.ear.plugin.version}&lt;/version&gt; &lt;configuration&gt; &lt;version&gt;5&lt;/version&gt; &lt;generateApplicationXml&gt;false&lt;/generateApplicationXml&gt; &lt;defaultLibBundleDir&gt;lib&lt;/defaultLibBundleDir&gt; &lt;modules&gt; &lt;webModule&gt; &lt;groupId&gt;de.project&lt;/groupId&gt; &lt;artifactId&gt;project.war&lt;/artifactId&gt; &lt;bundleDir&gt;/&lt;/bundleDir&gt; &lt;bundleFileName&gt;project.war&lt;/bundleFileName&gt; &lt;contextRoot&gt;project&lt;/contextRoot&gt; &lt;/webModule&gt; &lt;/modules&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/build&gt; </code></pre> <p>The package-impl, which is included in the EAR as JAR, has some Test Classes in it. Unfortunatly these Test Classes are bundled whith the JAR, when the EAR is assembled. Besides the facet, that Maven should inlucde the test classe, how can I exclude these Test classes in the JAR, when the EAR is assembled?</p> <p>All Test Classes in package-impl are in src/test/java Source Folder.</p> <p>Regards Sven</p> <p><strong>UPDATE:</strong> When I build the package-impl indepent from tha EAR manually the test classes are not included (as expected).</p> <p><strong>UPDATE2</strong></p> <p>Here is the complete package-impl POM.xml</p> <pre><code>&lt;project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"&gt; &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;artifactId&gt;project-impl&lt;/artifactId&gt; &lt;parent&gt; &lt;groupId&gt;de.company&lt;/groupId&gt; &lt;artifactId&gt;project&lt;/artifactId&gt; &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt; &lt;relativePath&gt;../project&lt;/relativePath&gt; &lt;/parent&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.spec&lt;/groupId&gt; &lt;artifactId&gt;jboss-javaee-6.0&lt;/artifactId&gt; &lt;version&gt;${jee6.version}&lt;/version&gt; &lt;type&gt;pom&lt;/type&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.hibernate.javax.persistence&lt;/groupId&gt; &lt;artifactId&gt;hibernate-jpa-2.0-api&lt;/artifactId&gt; &lt;version&gt;${hibernate.jpa-api.version}&lt;/version&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss&lt;/groupId&gt; &lt;artifactId&gt;jboss-vfs&lt;/artifactId&gt; &lt;version&gt;${jboss-vfs.version}&lt;/version&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;commons-lang&lt;/groupId&gt; &lt;artifactId&gt;commons-lang&lt;/artifactId&gt; &lt;version&gt;${commons-lang.version}&lt;/version&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;dom4j&lt;/groupId&gt; &lt;artifactId&gt;dom4j&lt;/artifactId&gt; &lt;version&gt;${dom4j.version}&lt;/version&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;javax.faces&lt;/groupId&gt; &lt;artifactId&gt;jsf-api&lt;/artifactId&gt; &lt;version&gt;${jsf-api.version}&lt;/version&gt; &lt;scope&gt;provided&lt;/scope&gt; &lt;/dependency&gt; &lt;!-- depenencies on third party modules --&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.solder&lt;/groupId&gt; &lt;artifactId&gt;solder-impl&lt;/artifactId&gt; &lt;version&gt;${jboss.solder.solder-impl.version}&lt;/version&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.seam.persistence&lt;/groupId&gt; &lt;artifactId&gt;seam-persistence&lt;/artifactId&gt; &lt;version&gt;${org.jboss.seam-persistence.version}&lt;/version&gt; &lt;exclusions&gt; &lt;!-- already provided by jboss as --&gt; &lt;exclusion&gt; &lt;groupId&gt;org.jboss.spec.javax.servlet&lt;/groupId&gt; &lt;artifactId&gt;jboss-servlet-api_3.0_spec&lt;/artifactId&gt; &lt;/exclusion&gt; &lt;/exclusions&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.richfaces.core&lt;/groupId&gt; &lt;artifactId&gt;richfaces-core-impl&lt;/artifactId&gt; &lt;version&gt;${jboss.richfaces.version}&lt;/version&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.richfaces.ui&lt;/groupId&gt; &lt;artifactId&gt;richfaces-components-ui&lt;/artifactId&gt; &lt;version&gt;${jboss.richfaces.version}&lt;/version&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.reflections&lt;/groupId&gt; &lt;artifactId&gt;reflections&lt;/artifactId&gt; &lt;version&gt;${org.reflections.version}&lt;/version&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.arquillian&lt;/groupId&gt; &lt;artifactId&gt;arquillian-bom&lt;/artifactId&gt; &lt;version&gt;1.0.0.Final&lt;/version&gt; &lt;scope&gt;import&lt;/scope&gt; &lt;type&gt;pom&lt;/type&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.arquillian.junit&lt;/groupId&gt; &lt;artifactId&gt;arquillian-junit-container&lt;/artifactId&gt; &lt;version&gt;1.0.0.Final&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt; &lt;artifactId&gt;arquillian-weld-ee-embedded-1.1&lt;/artifactId&gt; &lt;version&gt;1.0.0.CR3&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.jboss.weld&lt;/groupId&gt; &lt;artifactId&gt;weld-core&lt;/artifactId&gt; &lt;version&gt;1.1.5.Final&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.slf4j&lt;/groupId&gt; &lt;artifactId&gt;slf4j-simple&lt;/artifactId&gt; &lt;version&gt;1.6.4&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;junit&lt;/groupId&gt; &lt;artifactId&gt;junit&lt;/artifactId&gt; &lt;version&gt;4.8.1&lt;/version&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/project&gt; </code></pre> <p><strong>UPDATE3</strong></p> <p>This ended up to be an eclipse setting. The EAR-Project had a list of folders which contained the test folder.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTunaki
    1. USsvenkubiak
    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
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat does it mean jar has test classes inside? It shouldn't. There should be only compiled main classes inside. Is this `package-impl` artifact also build by Maven?
      singulars
      1. POExclude Test Classes in dependend Maven JAR
      1. USMichał Kalinowski
    2. COIf you have test classes inside a EAR/JAR than you are not using the defaults. There is something strange in your configuration. usually in the jar no test classes will be packaged into.
      singulars
      1. POExclude Test Classes in dependend Maven JAR
      1. USkhmarbaise
    3. CO@Michal Kalinowski The package-impl has TestCases which are (for some reason) compiled as java classes and packed into the package-impl JAR which is a dependent of the EAR Project. And yes, the package-impl is also build with Maven.
      singulars
      1. POExclude Test Classes in dependend Maven JAR
      1. USsvenkubiak
 

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