[ 
https://issues.apache.org/jira/browse/MNG-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792752#comment-16792752
 ] 

Markus Meisterernst commented on MNG-5614:
------------------------------------------

see: 
https://issues.apache.org/jira/browse/MNG-6608?focusedCommentId=16792724&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16792724

 

:)

> Continuous Delivery Friendly Versions not present in installed artifacts
> ------------------------------------------------------------------------
>
>                 Key: MNG-5614
>                 URL: https://issues.apache.org/jira/browse/MNG-5614
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>            Reporter: Axel Fontaine
>            Priority: Major
>
> Consider a parent pom with these tags:
> ...
> <version>${revision}</version>
> ...
> <properties>
>         <revision>0-SNAPSHOT</revision>
> </properties>
> ...
> If I start the build with:
>   mvn install -Drevision=666
> The revision gets replaced correctly at runtime (correct), but the 
> placeholder remains in the installed artifact in the local repository (wrong).
> To make matters worse, if you have a Maven Plugin child module with these 
> tags in the pom:
> ...
> <parent>
>         ...
>         <version>${revision}</version>
> </parent>
> ...
> <packaging>maven-plugin</packaging>
> ...
> <dependencies>
>         <dependency>
>             <groupId>${project.groupId}</groupId>
>             <artifactId>other-artifact</artifactId>
>             <version>${project.version}</version>
>         </dependency>
> </dependencies>
> Once the plugin gets used in yet another module, the resolution of 
> other-artifact will fail at runtime with:
>  Plugin ...:666 or one of its dependencies could not be resolved: Could not 
> find artifact ...:other-artifact:jar:0-SNAPSHOT
> Until this is fixed the functionality provided by MNG-5576 is virtually 
> useless.
> By speaking about the fix, why bother with replacing variables? Why bother 
> with parent POMs? How about simply installing and deploying the effective 
> POM? This would solve a whole range of problems at once. And at the end of 
> the day, this will simplify many things, at the cost of slightly larger 
> installed POMs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to