Richard S. Hall wrote:
John E. Conlon wrote:
Encountering maven bug
http://jira.codehaus.org/browse/MNG-1682 when building the trunk.
This is a subtle bug that often goes
undetected.
To see it you will have to check the console output from the build.
Look at the last line of each build to verify that a proper file
extension was used to store the bundle in the local repo.
[INFO]
Installing
/home/jconlon/projects/svns/felix/trunk/mosgi.jmx.httpconnector/target/org.apache.felix.mosgi.jmx.httpconnector-0.9.0-incubator-SNAPSHOT.jar
to
/home/jconlon/.m2/repository/org/apache/felix/org.apache.felix.mosgi.jmx.httpconnector/0.9.0-incubator-SNAPSHOT/org.apache.felix.mosgi.jmx.httpconnector-0.9.0-incubator-SNAPSHOT.osgi-bundle
To work around this I had to split up the trunk/pom-old-plugin.xml in to
3 files to isolate the
<module>ipojo.arch</module>
from the rest of the modules.
Shall I open an issue on Jira?
Yeah, this is basically a known issue. I thought we had it fixed by
splitting the pom.xml in two...are you seeing still seeing it in the
trunk with the two pom files?
Yes. I see it when I run the ant build which uses the two pom.xmls
underneath. I would not have caught it if the build would have
completed.(and that can happen if one already has an older snapshot in
the repository, one that a latter project requires. This can induce hard
to find bugs.)
In order to keep the sequence as I noted I had to split
pom-old-plugin.xml in to
3 files. The first builds all modules up to ipojo.arch, the second just
ipojo.arch the third all the rest. AFAIK the bug kicks in when more
than two packaging types are uses in the multiproject. In this case
ipojo has does a <packaging>ipojo-bundle</packaging> which triggers the
bug.
Anyone know when maven developers will fix this blocker? (It's labeled
Major, but it should be Blocker - Hey were forced to use Ant here!)
John
