Hi Jörg, > We use simply "x-SNAPSHOT" for the parent version. That way no > unreleased project has to be touched, it simply uses the "lastest" > SNAPSHOT of the parent. No script required.
Yeah, that is very convenient, if you are willing to accept the two-edged sword of irreproducible builds. A breaking change in the parent will break all builds that consume it... but can be fixed just as easily too without touching the downstream projects. Of course, it's a decision every project has to make for themselves. My projects opted for build reproducibility by using only release linkages (for parent POMs, dependencies and plugins). This has many advantages: e.g., "git bisect" fully works as one might hope, allowing you to resurrect the state of the code even from years prior and still build successfully. The downside is that you must make releases in order to be able to pin to them. Regards, Curtis On Tue, Feb 4, 2014 at 4:38 AM, Jörg Schaible <joerg.schai...@swisspost.com>wrote: > Curtis Rueden wrote: > > > Hi everyone, > > > >> > The very point I am trying to make here is > >> > "how do you manage that manual BOM on a daily basis". > >> > >> There is no automatic solution for this that I know of. > > > > Maybe not exactly what you are looking for, but sort of similar: > > > > My group uses a script [1] to automatically bump the version of our > parent > > POM [2]. > > We use simply "x-SNAPSHOT" for the parent version. That way no unreleased > project has to be touched, it simply uses the "lastest" SNAPSHOT of the > parent. No script required. > > [snip] > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
