Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.7
-
None
-
None
Description
As discussed in http://jira.codehaus.org/browse/MPWAR-30 , there are many situations when it's convenient to pack the project's JAR inside its WAR.
Besides the reasons quoted in that Maven issue, I found another one related to Cactus: I had a project where we create some Maven tasks that call cactifyear to create the EAR, unzip it on JBoss and generate the Eclipse meta files in a way that we can change the Cactus classes without redeploying it. But in order for it to work, I cannot have the projects classes on WEB-INF (neither on lib or classes), so in that case I would need:
maven.war.usesJar=true
cactus.war.includesJar=false
Anyway, independently of the outcome of MPWAR-30, we could add the cactus.war.includesJar property on Cactus.
– Felipe
Cactus in particular has another need:
In the Cactus arena, in particuar