2010/8/31 Nathan Bubna <[email protected]>: >>> And finally, i >>> don't know if maven can do this, but one of my current favorite parts >>> of the Velocity and VelocityTools build files is that they spit out >>> customized directions for building and publishing releases right along >>> with the target output, including what documentation to be sure and >>> update. That really helps to keep me on track when i'm doing >>> releases. >> >> Can you make an example, or tell me where to see? I missed this point. > > sure, in Engine, call the ant release.howto and publish.howto targets
Ah echos! It is possible with... Antrun plugin! :-D Anyway, reading the readme.howto directions, most of them are automatically done when calling: mvn release:prepare and mvn release:perform In particular, tagging, signing, moving to the next version, publishing to Nexus and to people.apache.org are automatically done. RAT check can be attached, if we want. Anyway, what difference do you see in reading this text and reading an HTML page like this? http://tiles.apache.org/framework/dev/release.html >>> Also, i'm curious whether any of these builds include OSGi manifest >>> creation? That's a recent addition to some of our builds (just engine >>> and tools at this point, i think), that i don't want to lose. >> >> It is possible (I've already done it with Tiles) however I forgot to put it. >> Did you publish any of these OSGi-ready packages, so I can configure >> the plugin correctly? > > yeah, i think both Engine 1.6.4 and 1.7-beta1 supported it, though > with different techniques, IIRC. The Engine's build uses Spring's > Bundlor ant task for it. I think some osgi stuff was in Tools 2 also. Sorry to contradict you, but I see it only in 1.7-beta1. Anyway it is pretty straightforward, it's easy to configure with the Maven Felix plugin. Thanks Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
