[
https://issues.apache.org/jira/browse/CACTUS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petar Tahchiev updated CACTUS-223:
----------------------------------
Fix Version/s: (was: 1.8)
> Allow inclusion of the project's JAR into Cactu's WAR
> -----------------------------------------------------
>
> Key: CACTUS-223
> URL: https://issues.apache.org/jira/browse/CACTUS-223
> Project: Cactus
> Issue Type: Improvement
> Components: Maven Integration
> Affects Versions: 1.7
> Reporter: Felipe Leme
> Assignee: Felipe Leme
> Priority: Minor
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
