[ 
https://jira.codehaus.org/browse/MCOMPILER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332166#comment-332166
 ] 

SebbASF commented on MCOMPILER-213:
-----------------------------------

I suggested checking the pom timestamp as that seemed to be a way of providing 
what the OP wanted.

A build that uses make(1) can specify that the build depends on the makefile, 
so that changes to it force a rebuild.

Maybe there is some scope for adding a list of files whose timestamps are 
checked by the compiler plugin?
It would then be possible to extend this by adding plugins to extract and store 
whatever metadata is appropriate, only updating the store if the metadata has 
changed. The compiler could then check that timestamp.
                
> 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

Reply via email to