Why does mvn always install a new jar file when the original jar file
did not change? Would be nice if it could skip this step to speed up
large multi-module builds when only single module (or few modules)
have changes.
Same goes for handling copying resources... seems like mvn spends a
bunch of time copying them (usually when filtering is enabled) when
there are no changes to be made. In Ant terms I could have use a n
uptodate task and a linked target to only copy (or install) these
things when something has changed.
Why has Maven moved away from this kind of handling of build tasks?
Re-running a build takes much, much longer than is really needed in
many cases, especially when only a class here and there is changed.
Are there any plans to address some of these issues and hopefully
speed up rebuilds for Maven projects?
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
