Thanks, this is not ideal but does give me a super fast build! Again, it'd be real nice to have this as a per dependency tunable...
-aps On 9/4/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
This is normal behavior for Maven -- it searches the repo once a day (more or less, depending on your configuration settings) to make sure there are no updates to any dependencies or plugins that it needs to download before running your build. You can specify -o for "offline" ie "mvn -o package" (unsure how this is done in Eclipse + M2) which will keep M2 from checking for updates, to increase the speed of your builds. Wayne On 9/4/06, Alexander Sack <[EMAIL PROTECTED]> wrote: > I've just started using Maven2 with Eclipse on a big project and so far so > good. One odd thing though, I've had to import some dependencies in my > local repository using mvn install:install-file goals. However, when I > execute mvn, it still searches the default repo even though they are > locally. Why is that? It makes the build much slower than I would have > liked. > > Btw, I just saw Jason's email I can tell you that initally Maven 1 was > pretty tough to live with for me. Maven 2 is vast improvement (especially > on the Java EE side which I'm now using exclusively though the ejb plugiin > has to be updated for Java EE 5). > > Thanks guys! > > -aps > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
