[
https://issues.apache.org/jira/browse/FELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470288
]
John Conlon commented on FELIX-198:
-----------------------------------
Your right two split poms are better than three. I think one is still better,
if it can be done.
But I was wrong in 'blaming' my favorite dep manager iPojo. On closer
examination of our sequence of module executions it appears that this bug
manifests after N number of packaging types are used. From what I see N=3.
Once N=3 all subsequent modules will deploy with that packaging name as the
extension.
So it is not only the iPojo packaging but our two other maven plugins also must
be factored into the problem.
Been looking at the use of profiles to fix this so we could use a single pom
again but this would require the segregation of all modules that use the
different plugins as well as the jdk 1.5 profile we have for the mosgi modules.
Building then would require a couple of steps but they would all be maven
oriented.
WDYT?
> Build of trunk fails
> --------------------
>
> Key: FELIX-198
> URL: https://issues.apache.org/jira/browse/FELIX-198
> Project: Felix
> Issue Type: Bug
> Affects Versions: 1.0.0
> Environment: java version "1.5.0_06"
> Reporter: John Conlon
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: mychanges.patch, pom-old-pluginA.xml
>
>
> Encountering maven bug
> http://jira.codehaus.org/browse/MNG-1682 when building the trunk with
> pom-old-plugin.xml called from the ant build.xml.
> This bug occurs when more than two packaging types are used in a multiproject
> build. In this case ipojo does a <packaging>ipojo-bundle</packaging> which
> triggers the bug for all subsequent module builds.
> These module builds will only occur when running with a jdk1.5, as this will
> trigger the mosgi module builds.
> <profiles>
> <profile>
> <id>jdk1.5</id>
> <activation>
> <jdk>1.5</jdk>
> </activation>
> <modules>
> <module>mosgi.console.xxx...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
