So I added a snippet of configuration from here: http://jira.codehaus.org/browse/MJAR-7
But the same kind of configuration supplied to the source plugin does nothing (and it too rebuilds the source jar every time even though there are no changes). -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:20 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything Rebuilding this same module with -X -e turned on, I see this: [DEBUG] isUp2date: false (Input file E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\pom.properties is newer.) What exactly is this file and how does it get created? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:12 AM To: Maven Users List Subject: RE: maven constantly rebuilding everything So we regularly use "mvn install". I didn't think that did a "clean" anywhere in its lifecycle. And yes, I understand that if the sources have changed, it will recompile, etc on down the line, but there are not source file changes, no sync, just "mvn install" then up arrow and run it again and it will build up the jars again, here's a look at the output from the "up arrow" pass. Is this because of our use of snapshot versions or something? [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Backoffice Core Engine [INFO] task-segment: [install] [INFO] ---------------------------------------------------------------------------- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: E:\work\up-svcs\lty\proj\LTY-P200712\reportsdirectory ------------------------------------------------------- T E S T S ------------------------------------------------------- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [source:jar {execution: attach-source}] [INFO] Building jar: E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar [INFO] [install:install] [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT.jar to E:\work\m2\Repository\lty\backofficeCore\P20 0712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT.jar [INFO] Installing E:\work\up-svcs\lty\proj\LTY-P200712\backoffice\core\target\backofficeCore-P200712-SNAPSHOT-sources.jar to E:\work\m2\Repository\lty\backoffice Core\P200712-SNAPSHOT\backofficeCore-P200712-SNAPSHOT-sources.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 seconds [INFO] Finished at: Thu Nov 08 10:08:12 EST 2007 [INFO] Final Memory: 8M/254M [INFO] ------------------------------------------------------------------------ -----Original Message----- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 9:55 AM To: Maven Users List Subject: Re: maven constantly rebuilding everything What command are you running? If you start (or end) your builds with 'clean', it is only logical that Maven rebuilds everything. Also, if you checkout your sources from SCM, Maven can't see that there's no changes and therefor will build everything again. On Thursday 08 November 2007 15:49, EJ Ciramella wrote: > I've just noticed kinda a little delemma here. From build to build, > when NOTHING has changed inside module "A", I can see that its still > rebuilding the jar for this particular module. > > Is there any reason this should be happening? Like say it is set to > build a "snapshot" version? I think it would notice that the source > directory doesn't contain any changes and not build. > > Any help/suggestions would be greatly appreciated. -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
