Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » headless PDE build: how can I force resolution of a modified plugin?
headless PDE build: how can I force resolution of a modified plugin? [message #597958] Thu, 28 May 2009 20:09
William R. Swanson is currently offline William R. SwansonFriend
Messages: 10
Registered: July 2009
Junior Member
I'm using Eclipse 3.4.2 to do a headless PDE build
for a product where I'm importing a standard plugin
(org.eclipse.cdt.make.ui) as a source project and making
some minor changes to the plugin code.

What I'm seeing is that when I export the product from
within Eclipse (File->Export, Eclipse Product), it builds
as expected and the standard CDT plugin is replaced
with my modified version.

When running a headless build, however, the behavior isn't
determinstic: on some runs it's replaced and on other runs
the original version of the plugin is picked up.

Is there a way to force the headless build to resolve
the plugin correctly, or equivalently is there something
else I need to do (like specify a dependency or a
different version number on the modified plugin)?


Currently, my modified CDT plugin has the same version
number as the original; I've tried changing the version number
(e.g. incrementing it to 5.0.2, etc.) but this does not work
because something (maybe the CDT feature) is still looking
for the original version:

Problems during export
Unable to find plug-in: org.eclipse.cdt.make.ui_5.0.1.200902130801. Please
check the error log for more details.
Unable to find plug-in: org.eclipse.cdt.make.ui_5.0.1.200902130801. Please
check the error log for more details.


The product is defined as one feature, which includes the
modified plugin together with some other custom plugins.
The feature also includes the two "platform" features
(org.eclipse.cdt, org.eclipse.platform), and the product
invokes the org.eclipse.ui.ide.workbench application.


When I compare the output of a successful headless run with
a failed headless run, it appears that the eclipse.generateFeature
task is attempting to resolve the modified plugin, since I always
see the following in the build log output:

generateFeature:
[eclipse.generateFeature] Some inter-plug-in dependencies have not been
satisfied.
[eclipse.generateFeature] Bundle org.eclipse.cdt.make.ui:
[eclipse.generateFeature] Another singleton version selected:
org.eclipse.cdt.make.ui_5.0.1.200902130801

In the generated "build.xml" file for the feature, I see that
the "all.plugins" target either does or does not include
an entry for the modified CDT plugin, based on how the
plugin gets resolved.

<target name="all.plugins" depends="init">
<ant antfile="build.xml" dir="../../plugins/org.eclipse.cdt.make.ui"
target="${target}">
<property name="arch" value="x86"/>
<property name="ws" value="gtk"/>
<property name="os" value="linux"/>
</ant>
... other custom plugins ...
</target>


Any suggestions on what I should change to get the
modified plugin to be resolved consistently?
It's almost there, it's like I only need to specify
one more constraint to make it happen. :-)

--- WRS
Previous Topic:'Cloud' PDE style on our product in 3.5RC2
Next Topic:Recommended way to run 3.5 in headless mode
Goto Forum:
  


Current Time: Mon Jun 21 17:01:46 GMT 2021

Powered by FUDForum. Page generated in 0.01734 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top