Install plugin behaves incorrectly in grandchildren projects that has packaging
!= jar
--------------------------------------------------------------------------------------
Key: MINSTALL-38
URL: http://jira.codehaus.org/browse/MINSTALL-38
Project: Maven 2.x Install Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Niclas Hedhman
Priority: Critical
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.
--
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
