I have a webapp that is to be used as a war overlay. My packaging type is war. It produces myOverlayWebapp.war
I have a different webapp "myapp1" that depends upon this overlay... Works well. I have another webapp "myapp2" that needs to depend upon the classes within the overlay project at compile time but does not need to use the Web artifacts. To accomplish this I forced the Overlay project to produce a JAR and a WAR... (myOverlayWebapp.war and myOverlayWebapp.jar). The pom for the overlay project still has a packaging type of war. In my current project myapp2 I specify the overlay project as a compile time dependency by setting the "type" of the dependency to "jar". The problem with this is that the web artifacts are stll coming into mywebapp2 even though my dependency explicitly specified a JAR not a WAR. Do you have any ideas how I could depend upon the classes during the compile yet not pull in the web artifacts into myapp2? -- View this message in context: http://maven.40175.n5.nabble.com/War-overlay-trouble-for-Pom-that-produces-WAR-and-JAR-tp329411p329411.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
