You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2007/12/23 12:53:57 UTC

[jira] Updated: (MNG-3333) range specified dependencies don't work

     [ http://jira.codehaus.org/browse/MNG-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MNG-3333:
------------------------------

    Priority: Major  (was: Blocker)

ok, that could be well after I got the new laptop. 

Downgrading priority, it still seems odd that a soft requirement 1.0.4 will not need to consult the versions metadata, while a hard requirement on [1.0.4] requires it. I guess the hard dependency on 1 single version shall be handled differently than regular version ranges.


> range specified dependencies don't work
> ---------------------------------------
>
>                 Key: MNG-3333
>                 URL: http://jira.codehaus.org/browse/MNG-3333
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1
>            Reporter: Milos Kleint
>         Attachments: ranges.zip
>
>
> current 2.1-SNAPSHOT
> When a dependency is specified with version [1.0.4] the build of project fails, so does project loading in the IDE.
> Example project 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