First of all, thank you for your inputs snicoll.
snicoll wrote: > > The modules configuration is completely useless since the EAR plugin will > build the modules list using the dependencies section of your EAR project. > You are right :) I realized that, just a few minutes before you posted, after following these test cases in SVN http://svn.apache.org/viewvc/maven/plugins/trunk/maven-ear-plugin/src/test/resources/projects/ snicoll wrote: > > You have a test-jar without a scope test so the ear plugin tries to > package > it since it's not scoped properly. > Right, that's what seems to be happening. Here's a trimmed down version of the pom.xml which manifests the issue: <groupId>org.myapp</groupId> <artifactId>sample-maven-ear-app</artifactId> <version>0.1.0-SNAPSHOT</version> <packaging>ear</packaging> <name>Sample Maven EAR</name> <!-- Dependencies --> <dependencies> <dependency> <groupId>org.someapp.ejb</groupId> <artifactId>someejbapp</artifactId> <version>1.0.0</version> <type>ejb</type> </dependency> </dependencies> All i am trying to do is package "only" the someejbapp.jar into the EAR. I do not want the rest of the nested dependency to be packaged in the EAR. This nested dependency has the test-jar and i have no control over changing the scope of that test-jar. I have been searching the EAR plugin docs and haven't yet found a way to include only the someejbapp.jar in the EAR. Is it possible? Did i miss some existing documentation? -- View this message in context: http://www.nabble.com/maven-ear-plugin%3A-Always-throws-%22Embedded-error%3A-Unknown-artifact-type-test-jar-%22-tp21370128p21435283.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
