|
Re: Source features depends on non-referenced fragment [message #638751 is a reply to message #638740] |
Fri, 12 November 2010 13:03 |
|
Hi Thorsten,
Please file a bugzilla and attach the sample there. Things discussed here tends to get lost :-)
- thomas
On 11/12/2010 01:18 PM, Thorsten Meinl wrote:
> Hi all,
>
> We have a problem with automated source feature generation: the source
> feature suddenly depends on a fragment that is not included in the
> binary feature. I attached a minimal case.
>
> - de.plugin is a normal plugin
> - de.plugin.fragment is a fragment with de.plugin as its host. It has a
> platform filter (os=win32).
> - de.feature.plugin bundles de.plugin only (the fragment will be bundled
> in a different feature)
> - de.update contains de.feature.plugin only (no references to the fragment!)
>
> Now if you build the update site by invoking the site.p2 action the
> source feature of de.feature.plugin (de.feature.plugin.source.feature)
> suddenly has a dependency to the fragment de.plugin.fragment! And the
> platform filter on the fragment then prevents installation of the source
> feature. I believe this is a clear bug.
> Closing the fragment project prior to building the US works fine.
>
> Cheers,
>
> Thorsten
>
|
|
|
Powered by
FUDForum. Page generated in 0.02805 seconds