Conflicting ranges should break the build, and would break it in the first place. If it released OK in the first place with bounded ranges and your repo still has the artifacts, it can be released again. If the old ranges now won't release, you have a conflict to resolve in your tree.
On Tue, Oct 27, 2015 at 11:39 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Shoot me for not giving the full response. > > Release.properties is too hacky to contain all the info to be > restored/restored with modifications. > > Never mind that if you lost the release.properties file and had to resume > elsewhere you might get stuck. > > So in my view you need to stash the original range in the pom... XMLPI is > the logical holder as it is a processing instruction for the release plugin > (or versions plugin) > > You need to bump the lower limit to whatever the range got resolved to when > switching back to development. > > The only remaining issue is how would people resolve conflicts of multiple > dependencies all have conflicting hard ranges? (Ok you add excludes... But > still could get hairy... Ok likely alerting of potential issue too there) > > On Monday 26 October 2015, Fred Cooke <fred.co...@gmail.com> wrote: > > > In our case, we don't want the original range back exactly, we want the > > current version of that, ie, higher lower bound to currently released > > things. > > > > Do not forget the transient ranges that need to be locked in our modified > > pom, either. Without this any tooling would be severely limited in use. > > > > Fred. > > > > On Tue, Oct 27, 2015 at 11:02 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com <javascript:;>> wrote: > > > > > The idea I had in versions-m-p was to put XML PI with the original > range > > > beside the resolved value so that the range can be set back post > prepare > > > (see completionGoals) > > > > > > Oh where is my elusive time > > > > > > On Monday 26 October 2015, Bernd Eckenfels <e...@zusammenkunft.net > > <javascript:;>> wrote: > > > > > > > Am Mon, 26 Oct 2015 13:03:03 -0400 > > > > schrieb Benson Margulies <bimargul...@gmail.com <javascript:;> > > <javascript:;>>: > > > > > Do we have any tooling for this? In my imagination, the top pom > for a > > > > > product to be released could be auto-decorated with > > > > > dependencyManagement locks. > > > > > > > > I think besides the release-with-pom from the release plugin but also > > > > versions:resolve-ranges: > > > > > > > > > http://www.mojohaus.org/versions-maven-plugin/resolve-ranges-mojo.html > > > > > > > > Gruss > > > > Bernd > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > <javascript:;> <javascript:;> > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > <javascript:;> > > > <javascript:;> > > > > > > > > > > > > > > -- > > > Sent from my phone > > > > > > > > -- > Sent from my phone >
