You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Hobson (JIRA)" <ji...@codehaus.org> on 2007/05/17 19:00:58 UTC

[jira] Created: (MNG-2988) Ranges with inclusive upper bounds are not validated against metadata

Ranges with inclusive upper bounds are not validated against metadata
---------------------------------------------------------------------

                 Key: MNG-2988
                 URL: http://jira.codehaus.org/browse/MNG-2988
             Project: Maven 2
          Issue Type: Bug
          Components: Artifacts
    Affects Versions: 2.0.6
            Reporter: Mark Hobson
         Attachments: patch.txt

See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html

Patch attached.

-- 
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-2988) Ranges with inclusive upper bounds are not validated against metadata

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

Jason van Zyl updated MNG-2988:
-------------------------------

    Patch Submitted:   (was: [Yes])

> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
>                 Key: MNG-2988
>                 URL: http://jira.codehaus.org/browse/MNG-2988
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Mark Hobson
>            Assignee: Jason van Zyl
>         Attachments: patch.txt
>
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html
> Patch attached.

-- 
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-2988) Ranges with inclusive upper bounds are not validated against metadata

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

Brett Porter updated MNG-2988:
------------------------------

      Fix Version/s: 2.0.7
    Patch Submitted: [Yes]

> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
>                 Key: MNG-2988
>                 URL: http://jira.codehaus.org/browse/MNG-2988
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Mark Hobson
>            Assignee: Brett Porter
>             Fix For: 2.0.7
>
>         Attachments: patch.txt
>
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html
> Patch attached.

-- 
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-2988) Ranges with inclusive upper bounds are not validated against metadata

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

Jason van Zyl updated MNG-2988:
-------------------------------


>From Mark's email:

I'm working on tests for MRELEASE-177 which has led me to investigate
how ranges are resolved.  An example problem was [1.0,2.0] resolving
to 2.0 irrespective of the repository metadata.

This appears to be due to VersionRange.getSelectedVersion and
isSelectedVersionKnown which selects the upper bound if present and
inclusive.  DefaultArtifactCollector then blindly uses this without
consulting the artifact metadata.  Any idea why VersionRange special
cases this situation?  All the integration tests pass without it.

> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
>                 Key: MNG-2988
>                 URL: http://jira.codehaus.org/browse/MNG-2988
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Mark Hobson
>            Assignee: Brett Porter
>             Fix For: 2.0.7
>
>         Attachments: patch.txt
>
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html
> Patch attached.

-- 
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-2988) Ranges with inclusive upper bounds are not validated against metadata

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

Jason van Zyl updated MNG-2988:
-------------------------------


Please put the description in the issue. One the beauties of Mylar is working completely offline which is not possible with external reference to the actual issues. It's bad practice not to have the intact set of information associated with the issue itself.

> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
>                 Key: MNG-2988
>                 URL: http://jira.codehaus.org/browse/MNG-2988
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Mark Hobson
>            Assignee: Brett Porter
>             Fix For: 2.0.7
>
>         Attachments: patch.txt
>
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html
> Patch attached.

-- 
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-2988) Ranges with inclusive upper bounds are not validated against metadata

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

Brett Porter closed MNG-2988.
-----------------------------

    Resolution: Fixed

applied to trunk and branch

> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
>                 Key: MNG-2988
>                 URL: http://jira.codehaus.org/browse/MNG-2988
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Mark Hobson
>            Assignee: Brett Porter
>             Fix For: 2.0.7
>
>         Attachments: patch.txt
>
>
> See http://www.mail-archive.com/dev@maven.apache.org/msg67131.html
> Patch attached.

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