I'd like to release the MXMLBeans plugin so geronimo can have an
actual released plugin for the upcoming 2.0 release.
Here's my take on the state of the plugin:
1. with a clean repo, the MXMLBEANS-21 integration test fails
because, in part 1, it builds a jar, that is required to be in the
repo in part 2. THis doesn't seem to relate to the capabilities of
the maven-invoker-plugin in any way. However, if you build the jar
by itself first, the test passes. I don't think fixing the maven-
invoker-plugin or figuring some new convoluted way to use it should
prevent release of this plugin.
There are 5 open issues.
2. MXMLBEANS-35 appears to be a lack of understanding of how to use
maven rather than ant.
3. MXMLBEANS-38 is a real and serious problem that has probably been
around for many releases. As long as you don't use the xmlbeans
plugin in a war project it doesn't seem to be a problem.
4. MXMLBEANS-22 is a improvement wish. This has been dragging on for
a year with little apparent attempt to come up with a working patch.
5. MXMLBEANS-37 appears to be a maven repo issue that is resolved (?)
6. MXMLBEANS-18 is an unscheduled improvement wish.
Since the june 2.3.0 release two new capabilities have been added:
MXMLBEANS-21 combining sourceSchemas and xsdJars properties
MXMLBEANS-39 support noAnn and noVDoc settings in the plugin/
xmlbeans code generator. (This one is needed by geronimo).
Any objections if I release 2.3.1 shortly?
thanks
david jencks
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
