On Sun, May 10, 2009 at 3:09 PM, Joerg Hohwiller <jo...@j-hohwiller.de>wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > > >> You can use dependency management or properties to deal with omitting > the > >> dependencies. I personally never assume what will be contained in a > reactor > >> and structure my builds so that any module can always be built in > isolation. > >> Therefore, I can't see why you would want to omit the dependency for > >> something in a reactor that may not be in the reactor all the time. The > >> release plugin handles this for you when it's time to bump the versions. > > I see your point. But I am always building from toplevel. > Anyhow I am also dreaming of a cmd-option in maven 3 that enables > a mode where maven walks up to the loplevel pom (as far as locally > available) and creates the entire reactor while still building > just the module where it was invoked. This could solve the problem you > pointed out as well as many other problems, e.g. to do dependent builds > of local modules. relying on the reactor and giving up on being able to build the one project separately is very bad (read: completely breaks) any IDE integration. Milos
