[
https://jira.codehaus.org/browse/MCOMPILER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated MCOMPILER-21:
-----------------------------------
Attachment: MCOMPILER-21.patch
started with some ugly hacks for now.
Doing proper incremental build support actually contains of 2 steps.
The first one mainly kicks in if someone invokes a phase < package. In this
case the Artifact of the other module is a directory. In this case we check
whether the depending module is a path and if so, we check whether it contains
newer files. -> recompile all.
The second trick will be on the reactor level. We might check the md5 of the
dependencies and compare them with the md5 previously used. -> invoke clean if
something changed.
> compiler smarts
> ---------------
>
> Key: MCOMPILER-21
> URL: https://jira.codehaus.org/browse/MCOMPILER-21
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Reporter: Brett Porter
> Assignee: Mark Struberg
> Fix For: backlog
>
> Attachments: MCOMPILER-21.patch
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
