You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jira-importer (via GitHub)" <gi...@apache.org> on 2025/04/02 09:01:46 UTC

[I] [MINSTALL-38] Install plugin behaves incorrectly in grandchildren projects that has packaging != jar [maven-install-plugin]

jira-importer opened a new issue, #337:
URL: https://github.com/apache/maven-install-plugin/issues/337

   **[Niclas Hedhman](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=niclas)** opened **[MINSTALL-38](https://issues.apache.org/jira/browse/MINSTALL-38?redirect=false)** and commented
   
   Case in hand; https://scm.ops4j.org/repos/ops4j/projects/pax/
   
   Pax contains a handful of subprojects, which in turn contains subprojects and they are often of a custom packaging "bundle" or "osgi-bundle".
   
   When building for instance from pax/logging as the root, things work as expected and we get the following info;
   [INFO] [install:install]
   [INFO] Installing /home/niclas/dev/ops4j/projects/pax/logging/api/target/api-0.9.5-SNAPSHOT.jar to /home/niclas/.m2/repository/org/ops4j/pax/logging/api/0.9.5-SNAPSHOT/api-0.9.5-SNAPSHOT.jar
   
   But when building one level higher up, we get the following message;
   [INFO] [install:install]
   [INFO] Installing /home/niclas/dev/ops4j/projects/pax/logging/api/target/api-0.9.5-SNAPSHOT.jar to /home/niclas/.m2/repository/org/ops4j/pax/logging/api/0.9.5-SNAPSHOT/api-0.9.5-SNAPSHOT.bundle
   
   Note that when building the grandchild project, the file extension is equal to the \<packaging> argument, but if building a child project, it is the jar file we construct.
   
   This problem appeared not too long ago, and may not be the problem of the Install Plugin after all, and instead is somewhere in the inheritence mechanism that got screwed up. Whatever, the problem is huge as we have this in much larger commercial projects, where it is not feasible to build project by project, and the Continuous Integration setup must be populated with hundreds of projects instead of 3.
   
   
   ---
   
   **Affects:** 2.1
   
   **Issue Links:**
   - [MNG-1682](https://issues.apache.org/jira/browse/MNG-1682) Plugins do not honor the correct extension when run as a part of a multiproject build
    (_**"duplicates"**_)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [MINSTALL-38] Install plugin behaves incorrectly in grandchildren projects that has packaging != jar [maven-install-plugin]

Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #337:
URL: https://github.com/apache/maven-install-plugin/issues/337#issuecomment-2771901630

   **[Niclas Hedhman](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=niclas)** commented
   
   In our case, the multiproject build must be 2 levels deep.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [MINSTALL-38] Install plugin behaves incorrectly in grandchildren projects that has packaging != jar [maven-install-plugin]

Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #337:
URL: https://github.com/apache/maven-install-plugin/issues/337#issuecomment-2771901635

   **[Stephane Nicoll](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=snicoll)** commented
   
   It's indeed a reactor issue. See the related link for more information.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org