[ http://jira.codehaus.org/browse/MXMLBEANS-19?page=all ]

Corridor Software Developer closed MXMLBEANS-19.
------------------------------------------------

    Resolution: Fixed

This is more or less resolved and the Geronimo project has been using the 
change for a bit now. Since it's the last defect in the way of the 2.0.1 
release, we'll consider it completely resolved unless otherwise pointed out...

> Stax and stax-api dependencies are all wrong in plugin pom
> ----------------------------------------------------------
>
>                 Key: MXMLBEANS-19
>                 URL: http://jira.codehaus.org/browse/MXMLBEANS-19
>             Project: Maven 2.x Xmlbeans Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.0.1
>            Reporter: David Jencks
>         Assigned To: Corridor Software Developer
>             Fix For: 2.0.1
>
>         Attachments: no-stax-v2.patch, xmlbeans-plugin-pom.diff
>
>
> The conclusion of the discussion in MXMLBEANS-13 IMO missed the point.
> 1. xmlbeans does not in any way require stax, it includes its own stax 
> implementation.  Therefore the stax dependency should just plain be removed, 
> no questions asked. 
> 2. xmlbeans does require stax-api.  This should be an xmlbeans dependency, 
> not an xmlbeans plugin dependency.  See 
> http://jira.codehaus.org/browse/MEV-406 (be sure that one is applied first).  
>  stax-api dependency should also be removed from the xmlbeans plugin 
> dependencies.
> I'll attach a patch for this.
> This issue is inhibiting geronimo m2 migration.
> As noted in MEV-406, you can see the actual xmlbeans dependencies at 
> http://xmlbeans.apache.org/documentation/conInstallGuide.html, and they very 
> clearly DO NOT include stax.  Breaking this plugin to satisfy some other 
> projects problems seems like the road to complete m2 unusability to me.
> Geronimo and openejb m2 builds work for me (as far as they exist) with the 
> MEV-406 change, this change, and removal of all stax and stax-api 
> dependencies from geronimo and openejb poms.  This is what one would expect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to