I believe the root of the problem is that the plugins can't communicate with each other. Compile for example can't tell jar if it actually compiled anything. Someone discussed a proposal for this recently here: http://www.nabble.com/-PROPOSAL--maven-build-context-%28Shared-context-f or-Maven-components-and-plugins%29-tf3138440s177.html#a8698847
-----Original Message----- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Monday, February 26, 2007 9:37 PM To: Maven Developers List Subject: Mvn always install's jar when nothings changed? 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
