[
http://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209321#action_209321
]
Andreas Christoforides commented on MCOMPILER-21:
-------------------------------------------------
I think the priority of this issue should be higher.
In the case of a file deletion the file is not removed and still packaged. In
the case of a rename, both file versions are packaged. In my experience when
developers see these problems they start doing clean builds every time making
the build time several times slower. Imagine making a single file change and
rebuilding everything from scratch. It is issues like this that makes users get
the perception that Maven is slow.
These is not a problem only with the Maven compiler plugin because I believe it
also happens with the resources plugin.
> compiler smarts
> ---------------
>
> Key: MCOMPILER-21
> URL: http://jira.codehaus.org/browse/MCOMPILER-21
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Reporter: Brett Porter
> Priority: Minor
> Fix For: 2.3
>
>
> there are probably other ways we can make the compiler stale check smarter.
> List them out here if you think of them.
> 1) if a snapshot was resolved to a newer version, rebuild everything.
--
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
