Bertrand Delacretaz wrote: > I think we must keep the existing bricks-cms as is as an example of > ant-based builds for 2.1.x, and create a separate Mavenized version - > it will be clearer than mixing up both things, and the > application-specific code is very small anyway, so duplication won't be > a problem. >
If we had a m2 repository with cocoon 2.1.7 or 2.1.8, you could mavenize directly your app without boring with your ant build anymore. Thus it would be a good example of how easy it is to switch bricks-cms to different version of cocoon (everybody claim backward-compatibility. it's time to verify :-). Now to put the cocoon2.1.x jar into the apache m2 repository, there is no need of mavenize the whole process of cocoon: just take the m2 ant task and add a target to deploy the ant-builded jar into the repository. Since the dependencies didn't evolves too much in 2.2-dev, you could take the pom already written for 2.2 and adapt them to 2.1.x. WDYT ?
