maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MWAR-113) The ability to not package the actual war file
Date Sun, 07 Oct 2007 20:05:08 GMT


Stephane Nicoll commented on MWAR-113:

Well, it happens :)

No, there's no way to change that, except if you define your own lifecycle. However, I am
not sure it's a good idea to do what you're asking. I'll discuss that on the dev list.

> The ability to not package the actual war file
> ----------------------------------------------
>                 Key: MWAR-113
>                 URL:
>             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:
For more information on JIRA, see:


View raw message