[ http://jira.codehaus.org/browse/MWAR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187546#action_187546 ]
Haikal Saadh commented on MWAR-86: ---------------------------------- 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 <archive><manifestFile/> (MWAR-167), and stuff that's in <packagingExcludes> 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?) > Split the WAR file creation as a separate goal > ---------------------------------------------- > > Key: MWAR-86 > URL: http://jira.codehaus.org/browse/MWAR-86 > Project: Maven 2.x WAR Plugin > Issue Type: Improvement > Affects Versions: 2.0, 2.0.1, 2.0.2 > Reporter: Simone Gianni > Priority: Minor > Attachments: maven-war-plugin1.diff > > > It would be nice to have a separate goal that zips the WAR file. This way it > will be possible to write (and use) plugins that manipulates the WAR folder > before the WAR file is built (like applying patches, reorganizing site > structure and similar stuff). > Also, there are some plugins (like the cocoon deploy plugin) that actually > extend the war plugin to operate "in the middle". This could be avoided > (IIUC) adding these separate goal in the WAR plugin. > It should be quite trivial to do, I volunteer for trying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
