Practical question. What should be supported maven version range for new ITs introduced during 3.1.2 development, [3.1,)? This means we'd need to tag ITs, right? Otherwise it wouldn't be possible to successfully rerun ITs for 3.1 and 3.1.1, unless I am mistaken.
-- Regards, Igor On 2013-09-14 1:24 PM, Jason van Zyl wrote:
When a release fails like this it is annoying to have to rev back the version of the POM. I'm not sure who flipped the versions in the POM and while it's a little more visible to see what you're moving toward I prefer the pattern of: 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT I know this may not be obvious to the casual observer as they may think 3.1 is next, but I'm personally fine with that. Especially after a failed release because then I don't have to go change all the POMs (whether rolling back manually, using the release rollback, the version:set command, or whatever else). It's much easier to just fix what's necessary and carry on. Unless anyone objects I would like to go back this pattern, what I previously had, because it's far easier to manage. Ideally it might be nice if all the tools understood 3.1.z-SNAPSHOT but they don't an in lieu of that I would prefer not to diddle POMs after a failed release. Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ---------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
