Hey all, Here's an update at my attempt to release. I'm not sure what got through to the list so I may be a little redundant.
The short news is: success. Earlier this week I spent a night trying a test release of 2.3.0, mostly to learn and partly to see where we blocked. The good news is that I managed to generate all three elements: the bin, the src and the javadoc zipball. It therefore appears that we *can* make a complete release. Problems I had: 1) the src/ folder was not yet in 2.3.x but should be. I hope someone has committed that folder to the build and to trunk/ 2) the pom.xml which is generated in target/checkout/ (? not sure that was the location) was missing the groupID and version numbers in the assembler section so this maven plugin couldn't be found 3) running mvn javadoc:javadoc *after* the rest means that the tag on the generated javadocs is one step later than the code released. I was releasing 2.3.0-M1 and the javadocs ended up being 2.3.0-M2-SNAPSHOT everything else seemed to work. I tried to protect the release process by creating my own branch but still uploaded a bunch of stuff to lists.refractions.net. So there are some 2.3.0-M1 fragments out in the wild. I'm unfortunately on the move again so I probably won't be somewhere with a stable internet connection for the near future. However, I'd like to try my hand at making a formal release soon to see if you all have indeed fixed the build process. cheers, adrian ------------------------------------------------------------------------- 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
