You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Roussel (JIRA)" <ji...@codehaus.org> on 2007/07/06 10:30:13 UTC

[jira] Commented: (MNG-3091) rebuild project speed

    [ http://jira.codehaus.org/browse/MNG-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101438 ] 

David Roussel commented on MNG-3091:
------------------------------------

I would like to have this too.

I guess this is currently assumed to be done one a per-plugin basis, currently?  Which means all plugins have to implement the same logic, so that's why it works for compile, but not for tests.

However, since each module only produces one artifact, which should be based only on it's sources (?) then as long as the artifact is more recent than then sources, then all plugins can be skipped.

To avoid this behaviour, just do a clean build.

> rebuild project speed
> ---------------------
>
>                 Key: MNG-3091
>                 URL: http://jira.codehaus.org/browse/MNG-3091
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Bootstrap & Build
>    Affects Versions: 2.0.7
>            Reporter: geoff simpson
>            Priority: Minor
>
> When rebuilding a project (the clean flag not set) maven still runs all the unit tests and rebuilds all the artifacts. It would be much faster if it worked in a way similar to make/ant where the time stamp of the files was checked, if the files are not modified and the dependencies have not changed then the artifact should not be rebuild. This would speed up the build time especially for J2EE projects that have a lot of .ear files which each reference several other .war and .jar artifacts 

-- 
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