[jira] [Commented] (MINSTALL-191) Metadata for submodules seems to be incomplete
[
https://issues.apache.org/jira/browse/MINSTALL-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840670#comment-17840670
]
Dorian Vallant commented on MINSTALL-191:
-
[~cstamas] I don't understand exactly what you mean by "This is a user
mistake". The project layout uses [standard Maven convention for
groupId|https://maven.apache.org/guides/mini/guide-naming-conventions.html].
But even if I change the groupId for in all pom's to e.g. `at.dvallant.maven`
(without any subgroup), it doesn't work either. Maybe I misunderstood
something...
> Metadata for submodules seems to be incomplete
> --
>
> Key: MINSTALL-191
> URL: https://issues.apache.org/jira/browse/MINSTALL-191
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install
>Affects Versions: 3.0.0-M1, 3.0.0, 3.1.0, 3.1.1
> Environment: Apache Maven 3.8.8
> (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
> Java version: 11.0.18, vendor: Eclipse Adoptium
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-83-generic", arch: "amd64", family: "unix"
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: maven-install-plugin-bug.tgz
>
>
> maven-install-plugin 3.x (and maven-deploy-plugin 3.x too) seems to have a
> bug when generating maven-metadata-*.xml for submodules containing custom
> maven-plugins.
> With version 2.5.2 maven-install-plugin generates the local metadata as
> follows:
> {code:xml}
>
>
> at.dvallant.maven
> plugins
>
>
> 0.1.0-SNAPSHOT
>
> 20230831082036
>
>
>
> my-maven-plugin
> my
> my-maven-plugin
>
>
>
> {code}
>
> After upgrading to 3.1.1 (also testet with 3.0.0-M1, 3.0.0 and 3.1.0) the
> generated file looks this:
> {code:xml}
>
> at.dvallant.maven
> plugins
>
>
> 0.1.0-SNAPSHOT
>
> 20230831082207
>
>
> {code}
> A test-project to reproduce the issue is attached.
> To reproduce build the project by calling `mvn clean install` and then check
> the contents of
> `~/.m2/repository/at/dvallant/maven/plugins/maven-metadata-local.xml`.
> If you downgrade the version to 2.5.2, metadata generation works as expected.
> If you could give me a hint where the problem might be in the code I can try
> to fix it and open a pull request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MINSTALL-191) Metadata for submodules seems to be incomplete
Dorian Vallant created MINSTALL-191:
---
Summary: Metadata for submodules seems to be incomplete
Key: MINSTALL-191
URL: https://issues.apache.org/jira/browse/MINSTALL-191
Project: Maven Install Plugin
Issue Type: Bug
Components: install:install
Affects Versions: 3.1.1, 3.1.0, 3.0.0, 3.0.0-M1
Environment: Apache Maven 3.8.8
(4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Java version: 11.0.18, vendor: Eclipse Adoptium
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-83-generic", arch: "amd64", family: "unix"
Reporter: Dorian Vallant
Attachments: maven-install-plugin-bug.tgz
maven-install-plugin 3.x (and maven-deploy-plugin 3.x too) seems to have a bug
when generating maven-metadata-*.xml for submodules containing custom
maven-plugins.
With version 2.5.2 maven-install-plugin generates the local metadata as follows:
{code:xml}
at.dvallant.maven
plugins
0.1.0-SNAPSHOT
20230831082036
my-maven-plugin
my
my-maven-plugin
{code}
After upgrading to 3.1.1 (also testet with 3.0.0-M1, 3.0.0 and 3.1.0) the
generated file looks this:
{code:xml}
at.dvallant.maven
plugins
0.1.0-SNAPSHOT
20230831082207
{code}
A test-project to reproduce the issue is attached.
To reproduce build the project by calling `mvn clean install` and then check
the contents of
`~/.m2/repository/at/dvallant/maven/plugins/maven-metadata-local.xml`.
If you downgrade the version to 2.5.2, metadata generation works as expected.
If you could give me a hint where the problem might be in the code I can try to
fix it and open a pull request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565026#comment-16565026
]
Dorian Vallant commented on MNG-6394:
-
@[~khmarbaise]: Is there any chance this issue will be solved in the near
future? Or does any workaround exist?
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar,
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524132#comment-16524132
]
Dorian Vallant commented on MNG-6394:
-
Are there any news to this issue?
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar,
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dorian Vallant updated MNG-6394:
Attachment: test-projects-flatten.jar
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar,
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449356#comment-16449356
]
Dorian Vallant commented on MNG-6394:
-
Same example with maven-flatten-plugin included...
[^test-projects-flatten.jar]
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar,
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dorian Vallant updated MNG-6394:
Comment: was deleted
(was: Same example with maven-flatten-plugin included in parent's pom.xml...
[^test-projects.jar] )
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449353#comment-16449353
]
Dorian Vallant commented on MNG-6394:
-
Same example with maven-flatten-plugin included in parent's pom.xml...
[^test-projects.jar]
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dorian Vallant updated MNG-6394:
Attachment: test-projects.jar
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448064#comment-16448064
]
Dorian Vallant commented on MNG-6394:
-
Here we go... [^test-projects.jar]
for detailed instructions please see README.md inside jar
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dorian Vallant updated MNG-6394:
Attachment: test-projects.jar
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439016#comment-16439016
]
Dorian Vallant commented on MNG-6394:
-
I think so. I have configured flatten-maven-plugin in my parent-project's pom.
Do I have to configure it in child's pom too?
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6394) ${revision} and parent.releativePath
Dorian Vallant created MNG-6394:
---
Summary: ${revision} and parent.releativePath
Key: MNG-6394
URL: https://issues.apache.org/jira/browse/MNG-6394
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.3
Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
Reporter: Dorian Vallant
If the CI friendly ${revision} property is used it seems maven does not simple
replace the property with the given value.
Consider the following example:
parent-project/
pom.xml
child-project/
pom.xml
parent-project/pom.xml:
...
my.group
parentArtifact
${revision}
pom
...
child-project/pom.xml:
my.group
parentArtifact
${revision}
../parent-project
If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
child-project/pom.xml clean install' all works fine as long as the parent
project is present in the file system. But if you move the parent project to
another place, build & install it to your local repository and then try to
build the child project, maven tries to download the pom.xml of the parent
project but does not replace ${revision}. So maven complains about a missing
dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
