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

Christoph Läubrich commented on MNG-7516:
-----------------------------------------

If you can explain more I might came up with a solution :) 

But maybe my explanation is wrong (or it is a problem in my setup):
{code}
 <parent>
    <groupId>group.of.parent</groupId>
    <artifactId>artifact.of.parent</artifactId>
    <version>1</version>
    <relativePath>../..</relativePath>
  </parent>
{code}

And assume that my parents version also resolves to 1 as well then I get an 
error like this:

{code:java}
Non-resolvable parent POM for group.of.parent:artifact.of.parent:1: Could not 
find artifact and 'parent.relativePath' points at wrong local POM 
{code}

So it seems maven feels that, even if both resolve to the same version (one 
times cifriendly and one time static), they do not match. This *might* be a 
rare setup but has surprised me a bit.

Another case is if I use
 
{code:java}
 <parent>
    <groupId>org.eclipse</groupId>
    <artifactId>eclipse-platform-parent</artifactId>
    <version>${revision}</version>
    <relativePath>../eclipse-platform-parent</relativePath>
  </parent>

  <groupId>org.eclipse.equinox.p2</groupId>
  <artifactId>rt.equinox.p2</artifactId>
  <packaging>pom</packaging>
  <properties>
     <revision>1.2.3</revision>
 </properties>
{code}

it also fails, of course one cant inherit any property from the parent, but it 
would be useful to do so in the case one releases a bunch of projects and 
parent.version==importing.pom.version ...


> Support CI-Friendly-Versions in parent pom references
> -----------------------------------------------------
>
>                 Key: MNG-7516
>                 URL: https://issues.apache.org/jira/browse/MNG-7516
>             Project: Maven
>          Issue Type: New Feature
>            Reporter: Christoph Läubrich
>            Priority: Major
>
> I just noticed that one could use CI-riendly versions in the version of the 
> project but not in the version of the parent.
> Is there any reason for not supporting this?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to