Here's the pseudo code: 1 - Don't have to build new jar because everything is uptodate? Don't install - maybe this means install takes a new param true/false style on whether it needs to be installed or not. 2 - If local jar has newer timestamp - install.
Install only cares about local repository, right? It's deploy that looks across to the internal repository - and the only machine to do that is the build machine. About the process-resources solution - is that kind of info available? Can I track back via the profiles on the commandline to the files in question (where the profiles came from)? Am I missing anything? -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, November 12, 2007 12:06 PM To: Maven Users List Subject: Re: maven constantly rebuilding everything Sounds reasonable, but how would you do #2? One way I was thinking was "grab latest jar from repo, compare contents to just built jar (hash both and compare?)". Or did you have another plan? Wayne On 11/12/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > So the fix would be something like: > > 1 - Make process-resources look at the source of the activated profiles and > make sure they are newer than the templates and then (and only then) process > the templates. > 2 - Make the "install" plugin test what's in the repository is out of date > with the just built jar before installing. > 3 - Make the war plugin able to ignore/exclude maven generated files (such > as pom.properties) - this may/may not solve our war rebuilding issues. > > ??? > --------------------------------------------------------------------- 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]
