Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 440156

Summary:	Identify 2.0-style plug-ins
Product:	[Eclipse Project] PDE	Reporter:	Andy Thomas-Cramer <thomascramera>
Component:	Build	Assignee:	pde-build-inbox <pde-build-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	4.4	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andy Thomas-Cramer

2014-07-22 15:43:37 EDT

Beginning with Eclipse 4.4, as a result of the resolution of bug 407312, builds will (by default) fail in the presence of Eclipse 2.0-style plug-ins. 

A workaround is to explicitly install the additional plug-in "Eclipse 2.0 Style Plugin Support". 

However, presumably the best long-term solution is to update the 2.0-style plug-ins to use an OSGi bundle manifest.

In the absence of the workaround, the build can include output like this:

  generateFeature:
  [eclipse.generateFeature] The service Plugin converter could not be acquired.
  [eclipse.generateFeature] The service Plugin converter could not be acquired.
  [eclipse.generateFeature] The service Plugin converter could not be acquired.
  ...

In my case, the output includes 22 of those "could not be acquired" lines. 

I'd like to eliminate those errors by updating the 2.0-style plug-ins. But I don't know which ones have been found troublesome. Manual inspection of our long list of plug-ins outside the Eclipse target revealed that all had MANIFEST.MF files with OSGi Bundle-* entries.

Could each of the error messages above identify the plug-in for which the converter would be necessary?

Comment 1 Lars Vogel

2018-11-13 07:27:46 EST

Mass change for PDE Build bugs tagged with "helpwanted". PDE build is not actively enhanced, hence I close these bugs as wontfix. Please reopen if you want to contribute a patch.