geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anita Kulshreshtha (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2082) [m2] stax dependencies are all wrong
Date Mon, 05 Jun 2006 12:25:30 GMT
    [ ] 

Anita Kulshreshtha commented on GERONIMO-2082:

 I have tested jetty-builder with only xmlbeans as a dependency using the above 
--  xbean-2.0.0.pom 
--  and removing stax from xmlbeans-maven-plugin-2.0.pom (effect is same as installing the
above jar) 
     and it works. 
   However I am curious, if a dependency is missing from my plugin o.a.g.plugins, maven gives
an error listing my plugin in the path, i.e.
 Path to dependency:
       1) org.apache.geronimo.plugins:geronimo-packaging-plugin:maven-plugin:1.2.0
       2) org.apache.geronimo.modules:geronimo-deploy-tool:jar:1.2-SNAPSHOT
    When an excluded dependency of xmlbeans-maven-plugin is missing, it gives the following
message :
Path to dependency:
       1) org.apache.geronimo.modules:geronimo-jetty-builder:jar:1.2-SNAPSHOT
       2) stax:stax:jar:1.1.1-dev
       3) xmlbeans:xmlbeans-jsr173-api:jar:2.0-dev !

> [m2] stax dependencies are all wrong
> ------------------------------------
>          Key: GERONIMO-2082
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>     Versions: 1.2
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.2
>  Attachments: geronimo-no-stax.diff, openejb-no-stax.diff, xbean-2.0.0.pom, xmlbeans-maven-plugin-2.0.1-SNAPSHOT.jar
> The dependencies for xmlbeans and the maven xmlbeans plugins are all wrong.
> xmlbeans pom needs to depend on stax-api, see
> xmlbeans plugin needs to have stax-api and stax dependencies removed, see
> At this point we can remove all stax and stax-api dependencies from our (and openejb)
> I'll attach the modified xmlbeans pom, the modified plugin, and the patches to remove
all stax mentions from our poms.  I'd appreciate some verification of my results.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message