Thanks, David. I will try to see whether I am lucky ;-) For the samples, why not we create a seperate code base for it, if we want to "seperate" it with the OpenEJB build.
2010/10/26 David Blevins <[email protected]> > > On Oct 25, 2010, at 5:18 PM, David Blevins wrote: > > > Side note, the mvn release plugin doesn't seem to work well with our > setup. Will dig up our release process page and post it. > > This is the doc, but it looks out of date to me: > > http://openejb.apache.org/openejb-release-process.html > > This setup almost always fails for me: > > mvn release:prepare -Dusername=dblevins -Dassemble > > Typically I end up making a release branch by hand > > svn copy https://..../branches/openejb-3.0.x https:// > ..../branches/openejb-3.0.3 > > Then I check it out and run 'mvn release:prepare' and that usually fails, > so I commit the results manually. > > Usually there are some other things it misses, like the ant files > (build.xml in all the examples). So I grab those with the following: > > $ find . -name 'build.xml' -exec perl -i -pe "s/(3.0.3)-SNAPSHOT/$1/g" {} > \; > > Just to make sure nothing is missed and still has -SNAPSHOT in it, I used > the 'ack' tool to search: > > $ ack -- '-SNAPSHOT' > > Then when it comes to publishing I do like so: > > $ mvn install -Dassemble -Dmaven.test.skip=true > $ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx > > For some reason you have to build once completely or the deploy will fail. > Not sure what the deal is with that. > > > -David > > -- Ivan
