Le mercredi 15 septembre 2010, Benjamin Bentmann a écrit : > Hervé BOUTEMY wrote: > > Expected SNAPSHOT dependencies should be in the pom IMHO, since each bits > > of build info should be there so that "mvn compile" is sufficient. > > I agree that we need to aim for a short command line but I'm not > convinced the POM can help us here. To me, it looks like a valid use > case to build the same project/POM once with and once without snapshots. > For example, think about a project where the development policy is to > pick up only released versions of dependencies, e.g. in order to avoid > destabilizing downstream projects while the dependency snapshots for the > next versions are in flux. Still, they might want to have some CI build > that integrates the snapshots to allow for early feedback regarding the > qualiity of the next release. CI builds from the same sources, this is > why I was thinking about a CLI option. yes, there can be multiple builds, then CLI option is necessary (think at a "Gump-like" CI too, where everything is changed to LATEST)
> > But something I didn't think about properly are big products that > consist of artifacts from various different groupIds. When such a > product build is expected to consume snapshots from all its > dependencies, the proposed default value for -sv isn't appropriate and > developers would be required to explicitly list the coordinates. Apart > from being cumbersome, this makes it harder to synchronize a team of > developers to have them get the same build results. +1: that's my point with having something in the pom, which defines the "normal" build of the team > > I have no solution right now and need to think about this some more. > Maybe the settings.xml can help (my previous concern about using this > during a release can be easily solved by the rule that non-snapshot > projects never ever consume snapshot dependencies for ranges). I have no solution either :( Hervé > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
