Re: [I] [MWAR-86] Split the WAR file creation as a separate goal [maven-war-plugin]
jira-importer commented on issue #242: URL: https://github.com/apache/maven-war-plugin/issues/242#issuecomment-2967855218 **[Simone Gianni](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=simonegianni)** commented I parametrized the WarMojo with two booleans, one to create the folder structure, the other one to create the war file. Then I created a new mojo, WarOnlyMojo, goal war-package, that subclasses WarMojo setting only the boolean needed to produce the war file. This way, it's possible to act this way in a project pom.xml : org.apache.maven.plugins maven-war-plugin 2.0.2-SNAPSHOT false xpatch xpatch-maven-plugin 1.0-SNAPSHOT package xpatch org.apache.maven.plugins maven-war-plugin 2.0.2-SNAPSHOT package war-package Unfortunately I found no way to "merge" the two war plugin declarations in a single one, since : - Declaring two executions makes the plugin execute 3 time, once with the default way, and the other two with the customized configuration. - Declaring the configuration together with the executions, makes the plugin ignore the default configuration and execute once as normal, and then with the war-package goal. Anyway with this it's already possible to change the cocoon-deployer-plugin so that it does not extend the war mojo, does not suffer from the NPE caused more or less from what's described here http://www.mail-archive.com/[email protected]/msg60770.html, and makes it possible to stack multiple plugins to work on a war before it's compressed to a single file. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [MWAR-86] Split the WAR file creation as a separate goal [maven-war-plugin]
jira-importer closed issue #242: [MWAR-86] Split the WAR file creation as a separate goal URL: https://github.com/apache/maven-war-plugin/issues/242 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [MWAR-86] Split the WAR file creation as a separate goal [maven-war-plugin]
jira-importer commented on issue #242: URL: https://github.com/apache/maven-war-plugin/issues/242#issuecomment-2967855225 **[Haikal Saadh](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tunaranch)** commented Would implementing this mean that, war:exploded will actually generate a dir. that actually resembles the final war, extracted? atm, war:exploded does not process \\ (MWAR-167), and stuff that's in \ is actually copied in to the staging directory. It seems reasonable to expect that war:exploded willl give you an exploded directory with contents that should match the final war's. At the moment, this is not the case. (Should I log a separate issue for this?) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [MWAR-86] Split the WAR file creation as a separate goal [maven-war-plugin]
jira-importer commented on issue #242: URL: https://github.com/apache/maven-war-plugin/issues/242#issuecomment-2967855223 **[wargre](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wargre)** commented why not make the war:exploded goal binded with prepare-package phase? Edit : 2009-03-25 With maven 2.1 we've got a workaround \ \ \org.apache.maven.plugins\ \maven-war-plugin\ \2.0\ \ \ \Prepare WAR\ \prepare-package\ \ \exploded\ \ \ \ \ \src/webapp\ \ \ prepare-package ... do everything you want, precompile, change jsp, ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
