[jira] Created: (JAXEN-138) incorrect poms on ibiblio

incorrect poms on ibiblio
-------------------------

         Key: JAXEN-138
         URL: http://jira.codehaus.org/browse/JAXEN-138
     Project: jaxen
        Type: Bug

  Components: core  
    Versions: 1.1    
 Environment: all
    Reporter: Brian Ewins
 Assigned to: Brian Ewins
     Fix For: 1.1


http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:

"Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."

He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.

Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_57991 ]

Elliotte Rusty Harold commented on JAXEN-138:
---------------------------------------------

http://www.ibiblio.org/maven/jaxen/poms/ looks like Maven 1 poms to me. I'm not sure what you're loking at. I don't know anything about maven 2 POMs for jaxen.

Also Gregory Block  is wrong about jaxen's structure. There are no plugins. There's one monolithic code base that depends on everything. Breaking this up into a more modular system has been on the todo list for  a while now, but I doubt we'll get to it in time for Jaxen 1.1.


> incorrect poms on ibiblio
> -------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_57993 ]

Brian Ewins commented on JAXEN-138:
-----------------------------------

What he's referring to is that in maven 2 you can define some dependencies as being build-time only (that's what 'scope' is for) so that you don't pull them in as transitive dependencies when you're only depending on jaxen. It isn't about splitting jaxen into modules, just recording in the pom that not everything is required to use jaxen at runtime.

Now compare our project xml:
http://cvs.jaxen.codehaus.org/viewrep/jaxen/jaxen/project.xml?r=1.58

with what's up on ibiblio, eg:
http://www.ibiblio.org/maven/jaxen/poms/jaxen-1.1-beta-4.pom 

The one on ibiblio begins with '<modelVersion>4.0.0</modelVersion>'.
take a look at 'modelVersion' - not only is the modelVersion element just called 'version' in maven 1, the value refers to the maven 2 schema. All of the pom files there are for maven 2.


> incorrect poms on ibiblio
> -------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

     [ http://jira.codehaus.org/browse/JAXEN-138?page=all ]

Brian Ewins updated JAXEN-138:
------------------------------

    Summary: incorrect maven 2 poms on ibiblio are not from cvs  (was: incorrect poms on ibiblio)

I've changed the title to make it clearer what the problem is here Elliotte. I know we dont have m2 poms, but they've sprouted up on ibiblio, and don't seem connected with Peter deploying the corresponding jars.

I'm guessing one of the maven people has added them to support the m2 release, and its ended up with complaints about jaxen. I'd prefer we had /no/ poms on ibiblio than have random files appearing there unconnected to our releases; who should users complain to?

When I asked if we could fix this without upgrading to m2, I was referring to the method of deployment onto ibiblio (ie maven jar:deploy). Since we use maven 1, its hardly going to deploy maven 2 descriptors for us.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_58008 ]

Elliotte Rusty Harold commented on JAXEN-138:
---------------------------------------------

I'm not sure what's happening there. I guess some maven person went through and modified the poms, possibly automatically. We shoudl probably file a bug on this with maven and ask for our orignal poms back or something.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_58046 ]

peter royal commented on JAXEN-138:
-----------------------------------

I know the maven guys have a routine that auto-generates m2 poms from m1 project.xml's....

And speaking of m2, I took a look at converting the build to m2 this past weekend but gave up. There's too little documentation, especially on migrating, given that we have extra things in our build like cobertura and findbugs. If anything, going back to just an ant build seems most sensible.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_63261 ]

Brett Porter commented on JAXEN-138:
------------------------------------

Basically what happened here:
- m1 poms get automatically converted to m2 poms in /maven2/
- We changed /maven/ to map to /maven2/ to ease long term maintenance.
- This means m1 poms aren't accessible from ibiblio any more. This shouldn't be a problem, as m1 doesn't use them.

If this is causing an issue, or the conversion is wrong, let me know (you can file a bug at MEV under jira.codehaus.org). If it just looks different but appears to be correct in terms of data, everything should be fine.

In terms of what I can see here, you want to change the way it is converted - this can be done in m1 by adding:
<properties>
  <optional>true</optional>
</properties>

(or <properties><scope>test</scope>, or similar...). These have no effect on m1, but will be converted to m2 correctly.

BTW, Peter - let me know if I can help regarding converting to m2. There is admittedly little documentation on converting from m1 because there isn't a great migration path, but it is meant to be easy enough to start from scratch (in parallel to the existing build) without being any more time consuming than a migration, or an ant build. Some folks are working on organizing the documentation at the moment in the wiki.


> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_63329 ]

peter royal commented on JAXEN-138:
-----------------------------------

Brett, thanks for the offer of m2 conversion help -- I might hit you up on IRC about that when I get some free time to devote to it.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=comments#action_63349 ]

Brian Ewins commented on JAXEN-138:
-----------------------------------

If you're going to discuss this on irc, can you ping me? Adding a comment to this bug would do, I'll pop over if/when the mail comes in. If I'm not around, just don't wait for me. I'm just interested in listening in on this. Thanks!

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

     [ http://jira.codehaus.org/browse/JAXEN-138?page=all ]
     
Elliotte Rusty Harold closed JAXEN-138:
---------------------------------------

    Resolution: Won't Fix

I'm not convinced this is our bug. It really sound slike it's Maven that has the problem. Jaxen itself is just fine. If there's a specific action Jaxen can take short of moving to Maven 2, and the Maven folks tell us what that is, then we can do it.

Longer term I think we'll move to Maven 2 after 1.1; and presumably that will fix any remaining issues.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>          Key: JAXEN-138
>          URL: http://jira.codehaus.org/browse/JAXEN-138
>      Project: jaxen
>         Type: Bug

>   Components: core
>     Versions: 1.1
>  Environment: all
>     Reporter: Brian Ewins
>     Assignee: Brian Ewins
>      Fix For: 1.1

>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152495#action_152495 ]

Geoffrey Wiseman commented on JAXEN-138:
----------------------------------------

Well, since this doesn't seem to have happened yet, is there any interest in having an outsider do a Maven 2 conversion for you?  I might be persuadable (although I'd have to check out XOM to get a sense for what's required) before I make any commitments.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>                 Key: JAXEN-138
>                 URL: http://jira.codehaus.org/browse/JAXEN-138
>             Project: jaxen
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: Brian Ewins
>            Assignee: Brian Ewins
>             Fix For: 1.1
>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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

    [ http://jira.codehaus.org/browse/JAXEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172028#action_172028 ]

Elliotte Rusty Harold commented on JAXEN-138:
---------------------------------------------

Geoffrey,

Now would be a good time to do a Maven 2 conversion since the code's fairly stable and no other major work is happening at the moment. Possibly we could release a 1.1.3 that did nothing except upgrade to Maven 2.

> incorrect maven 2 poms on ibiblio are not from cvs
> --------------------------------------------------
>
>                 Key: JAXEN-138
>                 URL: http://jira.codehaus.org/browse/JAXEN-138
>             Project: jaxen
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: Brian Ewins
>            Assignee: Brian Ewins
>             Fix For: 1.1
>
>
> http://www.ctoforaday.com/archives/000049.html Gregory Block was blogging about experiences with maven 2, jaxen came up:
> "Which brings us neatly to jaxen. There's a flag that allows libraries to list other libraries as optional dependencies - so you'd think that a system that includes plugins for jDOM, dom4j, and xom would list them as being optional, so you don't end up with all three. Fat chance. Worse yet, jdom's got the xmlapi/xerces problem. So in the end, Maven will go to download jDOM, dom4j, and xom - and all of their dependent libraries. Solution? More exclusions to go with your exclusions, forcing them all to excluded so you can manually choose what you end up deploying."
> He's referring to the 'scope' element in v4 poms for maven2. This struck me as odd since we only use maven1, but checking on ibiblio I see the only poms we have up there are for maven2.
> Can we fix this without jumping to m2 ourselves?

--
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