Hi, apparently release:prepare does a bad job even on the tag that's used to perform the release, as a result I have one user complaining that there are 2.2.2 deployed poms that do refer 2.2.3-snaphost.
Two questions: * to fix this, is it simply ok to checkout the 2.2.2 tag, build and do a mvn deploy? * since the tag gets checked out during release:perform, I guess the release instructions do miss something about checking out the tag set-up by release:prepare and fix the poms? Does the release process need to be so ridicously complex and error prone? I'm not the kind of person that can follow a list of stuff to do without forgetting something, especially if each item reveals surprises and if there are hours of wait between one item and the next one. I simply loose concentration... Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
