I like the overall direction to release it separately. Do you plan to use it for our 2.0_M1 release?
I have a few comments: 1) Should we rename "plugins" to "maven-plugins" to be clear that it contains maven plugins? 2) Should we also consider the following renaming too? Maven groupId: org.apache.tuscany.plugins ==> org.apache.tuscany.maven.plugins Java package name: org.apache.tuscany.sca.tools.maven.compiler ==> org.apache.tuscany.maven.compiler 3) How about having the initial version as 2.0.0? Later on, we can try to see if we can get other plugins into this base, such as the osgi-based surefire plugin, and the our enhanced bundle plugin. Thanks, Raymond From: ant elder Sent: Monday, February 09, 2009 8:41 AM To: [email protected] Subject: Releasing the Tuscany Maven Eclipse compiler module Fixing TUSCANY-2818 (and TUSCANY-2806) I've the eclipse compiler module ready for a release. There's now a top level plugins folder at [1] and the eclipse compiler module trunk is at [2], there's a tag for a 1.0 release of the module at [3] and a maven staging repository at [4]. I've set this up to use the Maven release plugin as practice for TUSCANY-2813 and that makes it all quite easy to do, there's no distribution so we just need a tag and the maven repository, see the README at [5] for details. Please review, if there are no comments I'll start a release vote in a day or two. ...ant [1] https://svn.apache.org/repos/asf/tuscany/plugins/ [2] https://svn.apache.org/repos/asf/tuscany/plugins/trunk/maven-eclipse-compiler/ [3] https://svn.apache.org/repos/asf/tuscany/plugins/tags/maven-eclipse-compiler-1.0/ [4] http://people.apache.org/~antelder/tuscany/maven-eclipse-compiler-1.0/ [5] https://svn.apache.org/repos/asf/tuscany/plugins/trunk/maven-eclipse-compiler/README
