You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pether Sorling (JIRA)" <ji...@codehaus.org> on 2006/07/09 16:39:22 UTC

[jira] Commented: (MNG-2007) Exported POM still has dependency version ranges

    [ http://jira.codehaus.org/browse/MNG-2007?page=comments#action_69347 ] 

Pether Sorling commented on MNG-2007:
-------------------------------------

Have the same issue with with some values not evaluated in the dependency part of the exported pom, using a profile like the one below the determine a version number in dependencies.

<profile>
   <id>developer</id>
    <properties>				
       <version.qualifier>DEV-20060709</version.qualifier>
    </properties>				
</profile>

<dependency>
     <groupId>some.group</groupId>
     <artifactId>fnord</artifactId>
     <version>0.1.0-${version.qualifier}</version>	
 </dependency>     
		
Evaluates correctly during build but the exported pom contains the same version string as above unevaluated.

> Exported POM still has dependency version ranges
> ------------------------------------------------
>
>          Key: MNG-2007
>          URL: http://jira.codehaus.org/browse/MNG-2007
>      Project: Maven 2
>         Type: Bug

>   Components: maven-archiver
>     Versions: 2.0.2
>     Reporter: Matthew Beermann
>      Fix For: 2.0.5

>
>
> If you have a version range for one of your dependencies, then the exported POM (the one that's placed in the repository and in the jar itself) will still have a range there. This seems at odds with (one) point of exporting a POM, which is to have all the information you need to reconstruct the state of a build at a particular moment in time. Without knowing which version number was chosen, you can't be sure you're reconstructing the same build later.
> It also seems to be at odds with the behavior elsewhere in this exported artifact: the plugins section shows the actual version number used, and active profiles are quietly merged into the main POM.

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