|Re: Product IU generated to require org.eclipse.core.runtime bundles [message #536067 is a reply to message #536047]
||Wed, 26 May 2010 20:15
|| Thomas Hallgren
Registered: July 2009
It would help if you could add a bugzilla and attach a sample that can be used to reproduce the problem (and eventually
verify it's been fixed).
On 05/26/2010 08:24 PM, Peter Nehrer wrote:
> FWIW -- I ended up moving my *.product files out of features and into a
> releng project, then implementing custom build steps to create my
> product configurations using p2.publish.product. I wish I didn't have to
> resort to that -- Buckminster provides a very elegant solution (if I
> were able to figure out how to get it to do what I need it to do).
> On 5/25/10 11:03 AM, Peter Nehrer wrote:
>> Btw I confirmed that PDE Export of the product does the right thing --
>> no extra dependencies are added. Sadness... :-(
>> On 5/23/10 9:49 AM, Peter Nehrer wrote:
>>> I noticed that my product IU is generated to depend on
>>> org.eclipse.core.runtime, org.eclipse.core.jobs, and
>>> org.eclipse.core.contenttype even though none of my bundles/features
>>> require anything in those bundles. If I install my product-level feature
>>> alone, they don't get pulled in; if I install the product IU, they do
>>> get pulled in (because content.xml lists them as required).
>>> Does anyone know why this is happening (I'm not sure when it started but
>>> I could swear it only started recently -- I'm using the latest 3.6
>>> code)? Is there a way to avoid it? Any insight would be greatly
>>> appreciated. Thanks!
Powered by FUDForum
. Page generated in 0.02334 seconds