[ 
https://jira.codehaus.org/browse/MINSTALL-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MINSTALL-33.
----------------------------------

    Resolution: Incomplete
      Assignee: Robert Scholte

No feedback from user, so closing it.
Also this looks more like an old Maven core issue rather then something caused 
by this plugin.
                
> mvn install:install-file should create appropriate entries so that 
> dependencies with version ranges will use installed file.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MINSTALL-33
>                 URL: https://jira.codehaus.org/browse/MINSTALL-33
>             Project: Maven 2.x Install Plugin
>          Issue Type: Bug
>          Components: install:install-file
>    Affects Versions: 2.1
>         Environment: all
>            Reporter: Patrick Moore
>            Assignee: Robert Scholte
>
> when using {{install:install-file}} it should cooperate with the code that 
> handles versions that don't have an explicit version, but specify a version 
> range. For example, if I install {{hibernate-3.2.0rc4}}, and my {{pom.xml}} 
> has the hibernate dependency specified as:
> {code:xml}
>     <dependency>
>       <groupId>hibernate</groupId>
>       <artifactId>hibernate</artifactId>
>       <version>[3.2.0rc4,)</version>
>     </dependency> 
> {code}
> maven will complain that it cannot find the hibernate version {{3.2.0rc4}}. 
> However if the dependency is specified as :
> {code:xml}
>     <dependency>
>       <groupId>hibernate</groupId>
>       <artifactId>hibernate</artifactId>
>       <version>3.2.0rc4</version>
>     </dependency>
> {code}
> then the project builds successfully. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to