Why a module for producing the distro? +1 on the examples/sample apps - fun part is how to try and overlap that with Cactus. It should be deploying the examples as our test layer.
One possible idea is to have taglibs-example.pom extending taglibs-parent.pom then rdc-example.pom extending taglibs-example.pom that depends on rdc.jar. ie) we have examples as a group of things rather than examples inside each taglib. Hen On Sat, Jan 10, 2009 at 11:32 AM, Rahul Akolkar <rahul.akol...@gmail.com> wrote: > I'm planning on moving the RDC taglib to m2 this weekend. I'd like to > retain as much as the old distro flavor as possible since I think its > quite useful. Therefore, I think the best way to go about this is to > have a multi-module m2 build: > > * One module for the taglib jar > * One for the examples and sample apps war file > * One for assembling the distros (two: source and binary -- and as > before binary will contain, the above jar, war and tld, javadocs and > tlddoc) > * Probably a parent pom for <dependencyManagement> mostly > > Some experimentation involved, but I'd rather just do this on trunk. > As a result, the RDC trunk will be broken this weekend. Once I'm done > and the build is usable, I'll reply to this message. Must you need a > working base this weekend, you can get it off the PRE_M2 tag: > > http://svn.apache.org/repos/asf/jakarta/taglibs/proper/rdc/tags/PRE_M2/ > > -Rahul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: taglibs-dev-unsubscr...@jakarta.apache.org > For additional commands, e-mail: taglibs-dev-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: taglibs-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: taglibs-dev-h...@jakarta.apache.org
