You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/07/24 20:01:26 UTC

[jira] Created: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

POM validation fails on projects in central repo starting with 2.0.10 RCs
-------------------------------------------------------------------------

                 Key: MNG-3680
                 URL: http://jira.codehaus.org/browse/MNG-3680
             Project: Maven 2
          Issue Type: Bug
          Components: Artifacts and Repositories, Dependencies, POM
    Affects Versions: 2.0.10
            Reporter: John Casey
             Fix For: 2.0.10


use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Work logged: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_112449 ]

John Casey logged work on MNG-3680:
-----------------------------------

                Author: John Casey
            Created on: 24/Jul/08 04:32 PM
            Start Date: 24/Jul/08 04:31 PM
    Worklog Time Spent: 3 hours 
      Work Description: isolated the issue to a change in modello's handling of strict mode flag as it relates to invalid associations. I have an integration test, but it depends on bcel 5.1 at the moment, and *should* be rewritten to depend on a fictional project with an invalid dependency list like the one in bcel (this will isolate the test from any changes/problems related to bcel itself).

Issue Time Tracking
-------------------

            Time Spent: 3 hours
    Remaining Estimate: 1 hour  (was: 3 hours)

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 3 hours
>          Time Spent: 3 hours
>  Remaining Estimate: 1 hour
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Updated: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-3680:
----------------------------

    Fix Version/s: 2.0.10

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>             Fix For: 2.0.10
>
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Work started: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MNG-3680 started by John Casey.

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Work stopped: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MNG-3680 stopped by John Casey.

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Updated: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-3680:
----------------------------

              Assignee: John Casey
    Remaining Estimate: 0 minutes
     Original Estimate: 0 minutes

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Updated: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-3680:
----------------------------

    Remaining Estimate: 3 hours  (was: 0 minutes)
     Original Estimate: 3 hours  (was: 0 minutes)

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Closed: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-3680.
---------------------------

    Resolution: Fixed

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 3 hours
>          Time Spent: 3 hours
>  Remaining Estimate: 1 hour
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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

        

[jira] Commented: (MNG-3680) POM validation fails on projects in central repo starting with 2.0.10 RCs

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143061#action_143061 ] 

John Casey commented on MNG-3680:
---------------------------------

turns out this is a problem with the usage of the strict flag in the modello xpp3 plugin as it relates to associations.

the only way we can fix this problem in the 2.0.10 is to release a new version of the modello-plugin-xpp3 and use that to build Maven.

> POM validation fails on projects in central repo starting with 2.0.10 RCs
> -------------------------------------------------------------------------
>
>                 Key: MNG-3680
>                 URL: http://jira.codehaus.org/browse/MNG-3680
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, POM
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> use bcel:bcel:5.1 as a dependency, the pom is bad.

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