On Tuesday, June 19, 2012 9:52:25 AM UTC+2, rgoers wrote: > > This is really the wrong list to discuss how to address this. However, I > don't follow how a local copy followed by an update helps. You have to > modify trunk to commit the version change back. If for some reason the > release is bad (missing files, bad signature, etc) you need to roll it all > back even though it was already committed to source control and tagged. >
Yes, so modify another version of trunk and commit from there upon successful build of artifacts, followed by a copy back to your working trunk. This issue really only comes up in non-distributed SCM's (CVS, SVN etc.) and because snapshotting/versioning filesystems (ZFS, BTRFS etc.) aren't commonplace yet. Regardless of how this is achieved however, that is an implementation detail; I just pointed out a weakness in the usability of Maven and why the learning curve is steeper than it could've been. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/Tv8qZjVJIgwJ. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
