So how then does one know when they have to purge the local repository? And if it's important why isn't it done by default? Having rules where you sometimes need to and sometimes don't is really hard to live with. Perhaps you can clarify the rules? I would hate to tell the developers well add 'this' if you get 'that' error, etc.
If your building just one module of a large multi-module build I agree that OTHER modules not being built should be downloaded and used in the build. However, I'm saying that for the set of modules that I am building none should be downloaded. Yes, maven does download modules because that is the workaround I used to 'fix' the build. Since maven refused to build with the code in the module, when doing the multi-module build, I manually built and deployed the needed artifact and then maven saw it and used it in the build! Yeah, I should check the central repo to see if something is wrong there. This would explain what I am observing. -Dave On Fri, Apr 17, 2009 at 7:43 AM, Todd Thiessen <thies...@nortel.com> wrote: > > 4. We do not purge the local repo before a build (shouldn't have to). > > This is the only thing I disagree with. There are scenarios where you do > have to do it and it isn't obvious. > > > IMHO, muti-module builds shouldn't even try to download > > module artifacts for the build because by definition if your > > doing an install (or more) you are creating these... > > Not necessarily. You could build one module of a large multi-module > project and if that project has a dependency on another module, it would > need to download it. This can be a very valuable way to save dev build > time. > > I agree though that for a CI build, you want to build everything and > nothing should be downloaded. I didn't think anything was ;-). > > Perhaps the meta data of your snapshops in your central repo is > corrupted and maven thinks that these snapshots are always newer than > the ones built in your local. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
