[GRADLE-2627] Add support for Eclipse PDE Created: 11/Jan/13  Updated: 22/Nov/16  Resolved: 22/Nov/16

Status: Resolved
Project: Gradle
Affects Version/s: 1.3
Fix Version/s: None

Type: Improvement
Reporter: Remon Sinnema Assignee: Unassigned
Resolution: Won't Fix Votes: 1


The current Eclipse plug-in doesn't work well when the projects are OSGi bundles that are developed using Eclipse PDE:

  • Project dependencies should not be put on the .classpath as PDE handles them through the OSGi Import/Export-Package mechanism
  • External dependencies should be collected in the global Target Platform instead of in the individual .classpath files of all the projects

Comment by Johannes Bialek [ 02/Nov/13 ]

Hi, I'm currently working on a plugin for pde-builds from gradle. Your suggestions seem problematic to me as a target platform may only contain osgi-bundles and not generic java dependencies, furthermore the eclipse definition of target platforms is defined in the workspace (afaik) which is noch touched by the gradle plugin. My plan is to define a target-platform and the dependencies to bundles in a build.gradle such as in the example below:

pde {

{ directory new File('/Applications/eclipse 4.3/plugins') }


{ require name: 'org.eclipse.ui.forms', version: '3.5.200' require name: 'org.eclipse.ui' }


My plugin then resolves the bundle-requirements to jar files in the target-platform and adds them to the dependencies leaving the rest to the osgi-plugin (at least this is my idea).
The plugin adds the container "org.eclipse.pde.core.requiredPlugins" to the eclipse class path, so eclipse uses it's own way of resolving dependencies. This has the drawback that you have to define a target-platform both in gradle and the eclipse workspace.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Remon Sinnema [ 16/Nov/16 ]

This is no longer important too me.

Comment by Johannes Bialek [ 16/Nov/16 ]

This is no longer important to me as well.

Comment by Benjamin Muschko [ 22/Nov/16 ]

Based on your comments I am going to resolve the issue.

Generated at Wed Jun 30 12:27:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.