[
http://jira.codehaus.org/browse/MWAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109239
]
Stephane Nicoll commented on MWAR-113:
--------------------------------------
why don't you call war:exploded?
It does exactly that right?
> The ability to not package the actual war file
> ----------------------------------------------
>
> Key: MWAR-113
> URL: http://jira.codehaus.org/browse/MWAR-113
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1-alpha-1
> Environment: All
> Reporter: Bård Dybwad Kristensen
> Priority: Minor
> Attachments: maven-war-plugin-2.1-alpha-1-WIN-sources.jar
>
>
> My project uses jetty to run the web-application we package with Maven. Jetty
> uses the exploded version of the war, and the war file itself is not needed
> (not until we deploy on a Weblogic server, which will be done in system test
> and prod). But the developers does not need the war file. The war file itself
> is quite large (~70 Mb) and the packaging of the file takes quite a bit of
> time. This is unnecessary. So I made a small fix in the plug-in to solve this
> problem. I added a new parameter "packageWar" witth getters and setters in
> AbstractWarMojo, and did some refactoring in the WarMojo so that the
> packaging is only done if this parameter is set to true.
> I have added the code with the issue. Some tests fail with this new fix as
> they expect the war to be created. I have not altered any tests or added any
> tests. Just attaching the code and hope you guys think this is a good idea
> that should be included in some future release. The fix saves approx 30
> seconds up to a minute in our projects build cycle.
--
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
