[
https://issues.apache.org/jira/browse/FELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470559
]
Richard S. Hall commented on FELIX-198:
---------------------------------------
I am ok with that approach, because we can still have the ant.xml file that
builds all three profiles if we want, which makes it no worse than the current
situation.
I guess as far as how to segregate the subprojects, it depends on the nature of
the bug. If it is purely based on separating them so no single pom file uses
more than one packaging plugin at a time (as opposed to declaring more than one
packaging plugin at a time), then I guess Clement's suggestion would be
sufficient.
At this point, every subproject that uses the new plugin and/or no plugin can
be put into the first profile. Every subproject that uses the old plugin can be
put into the second profile. And then ipojo.arch should be put into the last
profile.
It is my goal to see us move all subprojects using the old plugin to the new
plugin, so once this happens we should just have two separate groups. Then once
the maven bug is fixed we can get back to a single pom file!
John, is this something you are going to contribute?
> 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.
