[
https://issues.apache.org/jira/browse/FELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470205
]
Richard S. Hall commented on FELIX-198:
---------------------------------------
Since iPOJO is causing the issue, since it introduces a second plugin, doesn't
it make more sense to create a pom-ipojo.xml file that contains that separates
all of the iPOJO-related projects into a single pom file? This is effectively
what we did with pom-new-plugin.xml, which separates the new plugin and the
projects that use it from the ones that don't. I assume that this approach
would solve the issue too, no?
> 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.
