maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Tolentino (JIRA)" <>
Subject [jira] Commented: (MWAR-26) Do not overwrite target unless source is modified
Date Tue, 21 Mar 2006 02:08:11 GMT
    [ ] 

John Tolentino commented on MWAR-26:

Maven 2.0.3 was already voted on for release. That email was sent by John Casey to maven developers
list, subject is [vote] Release Maven 2.0.3 (third RC).

So the libraries used in that 2.0.3 won't have any more changes. There will still be a patch
for maven-war-plugin in time for its 2.0 release though. Instead of having the code in plexus-utils,
it will be in the war plugin. We'll just have to apply the first patch when maven changes
the plexus-utils version that it uses to 1.2.

> Do not overwrite target unless source is modified
> -------------------------------------------------
>          Key: MWAR-26
>          URL:
>      Project: Maven 2.x War Plugin
>         Type: Bug

>     Reporter: Andres March
>     Assignee: John Tolentino
>      Fix For: 2.0
>  Attachments: MWAR-26-maven-war-plugin-2.diff, MWAR-26-maven-war-plugin.diff
>   Time Spent: 3 hours, 40 minutes
>    Remaining: 0 minutes
> I thought MWAR-8 had fixed my issue but it seems to still exist.  Correct me if I'm wrong
but doing incremental builds with this war plugin is not possible.  All the web app sources
get overwritten regardless if they have been modified or not.  Incremental build were possible
in Maven 1 because it was ANT based.  This version uses plexus FileUtils which overwrites
without regard to if the target file exists or older than the source.  Besides the time issue,
overwriting the web.xml each time makes my context reload since the context runs on tomcat
from the target location.  I think this is a reasonable configuration but if there is a better
way, let me know.  Building inplace wars is not an option as it dirties the source.
> If we are in agreement, I may be able to provide a patch.

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