[
https://jira.codehaus.org/browse/MCOMPILER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332159#comment-332159
]
Robert Scholte commented on MCOMPILER-213:
------------------------------------------
Verifying if the pom has changed is probably too expensive. A lot of elements
have no effect on source compilation. What should be verified is if any of the
sources has been changed and if all the compile arguments are exactly the same,
including the order of dependencies. There might be one challenge here:
checking non-unique SNAPSHOTs.
> maven compiler plugin doesn't detect change in pom.xml
> ------------------------------------------------------
>
> Key: MCOMPILER-213
> URL: https://jira.codehaus.org/browse/MCOMPILER-213
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.0, 3.1
> Environment: any
> Reporter: Jigar Joshi
> Priority: Minor
>
> Background:
> we are using maven build to build around 200 project tree, change in one
> single module costs building whole tree, to avoid it we switched to
> incremental build and I wrote a plugin that will periodically do full clean
> build after configurable period of time
> Issue:
> maven-compiler-plugin supports incremental compilation and only compiles the
> source that was modified that is nice feature, however it is not quite
> working well in following cases
> - if there is a change in pom.xml (for example:change in dependency scope),
> it doesn't detect it as change and doesn't recompile that and all effecting
> projects
> {{org.apache.maven.plugin.compiler.AbstractCompilerMojo.isDependencyChanged()}}
> should cover it
> Verified this on revision {{1495788}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
