On 05/22/2012 10:26 PM, Robby Pelssers wrote:
I find the documentation a bit scarce but at least it supports xslt2.0. If you come to think of it, Cocoon would be a super maven plugin supporting zipping, transforming, file writing, ... :-)
revision 1341870 I started with setup of the basic env that I was thinking about. It is still not 100% as I want and further ATM only in the block one.
salu2
Robby -----Original Message----- From: Robby Pelssers [mailto:robby.pelss...@nxp.com] Sent: Tuesday, May 22, 2012 5:22 PM To: dev@cocoon.apache.org Subject: RE: Keep archetype synced Was also thinking about using some kind of xsl transform to generate the archetype pom. I will take a look this evening how xml-maven-plugin works. Robby -----Original Message----- From: Thorsten Scherler [mailto:scher...@gmail.com] Sent: Tuesday, May 22, 2012 5:02 PM To: dev@cocoon.apache.org Subject: Keep archetype synced Hi all, as mentioned in another thread we need to find a way to manage the deps of the archetype in a less time consuming manner. Somehow we need to get the parents versions in the deploy of the archetype. We may want to look into doing some "magic" with <groupId>org.codehaus.mojo</groupId> <artifactId>xml-maven-plugin</artifactId> We used it in sobu to generate the i18n resource files based on xml, so we could use a archetype base.xml + xsl trans = final pom.xml This way we only need to keep in sync which deps we need the version would be taken from the parent.pom.xml. wdyt?
-- Thorsten Scherler<scherler.at.gmail.com> codeBusters S.L. - web based systems <consulting, training and solutions> http://www.codebusters.es/
