Hi Claude 2011/4/13 Claude Brisson <[email protected]>
> My last commit allows the use of tools-2.1-dev with engine-2.x (providing > one has done "mvn install" in his local engine-2.0.0-SNAPSHOT directory). > > It's only a temporary solution for us developers, since for now it requires > a manual replacement of three pom.xml by their respective alternate > pom.xml.engine2, and produces binaries which cannot be deployed since they > have the same name as the ones depending upon engine-1.6, whereas they would > need some kind of -engine2 suffix. > I noticed you removed the velocity-tools-view-engine2 module. If it was not clear, its purpose was to support Engine 2, in particular for some problems with its API changes. Wasn't it enough from your POV? Where did you find problems? > I'm not at all expert with Maven so I don't know yet how we can manage to > have modules but producing different archive names depending on a property > or a profile. > > No, it's better not complicate things. Either we remove Engine 1.x support completely, and release Tools 2.1 when Engine 2.0 is ready, or support both of them through separate modules. Profiles are not ideal to create different artifacts. Antonio
