Right, it is not. That is my scenario as well. This solution doesn't work for all use cases, but for the build server... We use CruiseControl so the core products are only built when CC detects a source control change. Therefore the jars only change when the code is built.
You can also use CC's build dependencies (see <buildstatus>) to trigger the dependent modules to build when a dependency changes. Obviously, this does not help any non-CC usage, such as developers. However, we use the IDE for ongoing development work, so it does not matter. And this doesn't mean that Maven shouldn't be enhanced... :-) HTH -----Original Message----- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 14, 2005 8:02 AM To: Maven Users List; [EMAIL PROTECTED] Subject: Re: Why are jar files rebuilt all the time? On 12/14/05, Anders Hessellund Jensen <[EMAIL PROTECTED]> wrote: > If you only want to compile your sources, try "mvn compile". "mvn > test-compile" compiles both main and test. These phases should run > pretty fast. In a multiproject environment this is typically not sufficient, isn't it? Jochen -- Often it does seem a pity that Noah and his party did not miss the boat. (Mark Twain) --------------------------------------------------------------------- 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]
