In the recent past, we have moved the maven plugins to become a
separate Tuscany sub-project with it's own releases. After that
happened, I have started to see a last minute rush to release these
plugins every time a Tuscany release is being created, and sometimes
we still release with a dependency on a SNAPSHOT version of these
plugins.

maven-bundle-plugin - Release 1.0.3 available
maven-eclipse-compiler - Release 1.0 available
maven-java2wsdl-plugin - Obsolete for now (remove in 2.x)
maven-osgi-junit - no release yet and the plugin has dependency on
tuscany node launcher. 2.x have SNAPSHOT dependency on this
maven-tuscany-plugin - ???
maven-wsdl2java-plugin - Generate java artifacts based on OSOA spec.
2.x uses wsimport (Remove in 2.x)
maven-zip-plugin - ??? Obsolete for now (remove in 2.x)

IMO, the benefits of having these plugins as a Tuscany sub-project is
not worth, compared with the issues and difficulties it's bringing to
the release process. To avoid further problems in the future releases,
I'd like to discuss the idea of moving them back to the main 2.x
build/release.


-- 
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Reply via email to