Details
-
Type:
Wish
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.1
-
Fix Version/s: 2.1.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
I am trying to justify a migration from a legacy build system to maven2, and am in the middle of a POC doing so. However, I have run into a roadblock in that we use XMLBeans 2.1.0 which looks to be in development but not yet released. I have a hack for it (see below) but for my organization to adopt maven2 it needs to support the versions of the 3rd party libraries we have like this 'out of the box' and without my hack-ish intervention.
I know next to nothing about XMLBeans as I haven't personally used it, but I would be happy to look at the differences that need to be exposed between the 2.0.0 and 2.1.0 schema compilers and integrate them into the plugin.
I've included the patch below for my trivial and silly "fix," though I suspect there are new features that need to be exposed as well that I'm not currently aware of. I did not see a tag/branch for 2.1.0 and checked out the code from https://svn.codehaus.org/mojo/trunk/mojo/xmlbeans-maven-plugin.
$ svn diff pom.xml
Index: pom.xml
===================================================================
— pom.xml (revision 2386)
+++ pom.xml (working copy)
@@ -199,7 +199,7 @@
<dependency>
<groupId>xmlbeans</groupId>
<artifactId>xbean</artifactId>
- <version>2.0.0</version>
+ <version>2.1.0</version>
<scope>compile</scope>
</dependency>
<dependency>
I've stopped using the Maven XmlBeans plugin until it can support XMLBeans 2.2.0. Ideally, it should inherit the version of XMLBeans to use to compile the API from the project's pom.