Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Partial success of PDE build on 3.5M6
Partial success of PDE build on 3.5M6 [message #593402] Wed, 18 March 2009 21:44
michael.sacarny is currently offline michael.sacarnyFriend
Messages: 103
Registered: July 2009
Location: USA
Senior Member
We have a Product based on the Niefer Headless Build example
(com.acme.rcp) modified to be Feature based. Here is a summary of my
experience attempting to PDE Build this with SDK 3.5M6 and Delta 3.5M6
using Run Configurations on a .launch file.

Summary:
* Installation of Delta Pack seems to have changed.
* Run Configurations build apparently fails in target eclipse.brand of
assemble.org.eclipse.pde.build.container.feature.win32.win32 .x86.xml if I
use a custom Progam Launcher Name. The exact failure is
java.io.EOFException.
* If I use the default Program Launcher name, I must add several apache
and ecf plugins for the build to complete.
* Build 'succeeds' but there is no eclipse.exe launcher in the package.
* If I Import org.eclipse.equinox.executable into my workspace and add it
to the Product Feature list, eclipse.exe is now finally in the package.
Still can't build with custom Program Launcher name, though.

- What is the correct install of Delta pack for headless PDE builds?
- Has anyone found a solution to the custom Program Launcher problem?
- Is the log message "ProvisioningEventBus could not be obtained. Metadata
caches may not be cleaned up properly." serious?

Thanks!
msacarny

Detailed notes:
1. The technique of laying the Delta on top of the SDK generates many
errors of the type:
!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-03-10 12:30:58.829
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the
filename property.
* Instead, I edit the Target Platform in Window, Preferences, Plugin
Development, Target Platform, AddÂ…, and specify the Directory of Delta
pack.
2. When I Run my Product build in Run Configurations, the build fails in
the customAssembly step after jarIng my main plugin. The console shows:
BUILD FAILED
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\productBuild.xml:31:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \build.xml:104:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\Builder\customTargets.xml:12: The following
error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\allElements.xml:10:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \genericTargets.xml:175:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.all.xml:23:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.all.xml:15:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\allElements.xml:44:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.win32.win32.x86.xml: 96:
java.io.EOFException

* The log associated with the error shows initially some MESSAGES of the
form:
!ENTRY org.eclipse.osgi 2 0 2009-03-18 15:50:10.984
!MESSAGE The following is a complete list of bundles which are not
resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-03-18 15:50:10.984
!MESSAGE Bundle
org.eclipse.core.filesystem.hpux.ia64_32_1.0.0.v20080604-140 0 [57] was not
resolved.

* I'm on Win32, x86, though, and I don't see a MESSAGE for that. Might be
ok.

I see one troubling entry like this:
!ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2009-03-18
15:50:11.203
!MESSAGE ProvisioningEventBus could not be obtained. Metadata caches may
not be cleaned up properly.

The hard error is here:
!ENTRY org.eclipse.osgi 4 0 2009-03-18 15:50:14.141
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
:
Caused by:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\productBuild.xml:31:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \build.xml:104:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\Builder\customTargets.xml:12: The following
error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\allElements.xml:10:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \genericTargets.xml:175:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.all.xml:23:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.all.xml:15:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\org.eclipse.pde.build\scripts \productBuild\allElements.xml:44:
The following error occurred while executing this line:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.win32.win32.x86.xml: 96:
java.io.EOFException
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:508)

* And further down:
Caused by:
C:\eclipse\VisualDSP\workspace\output\productBuild\assemble. org.eclipse.pde.build.container.feature.win32.win32.x86.xml: 96:
java.io.EOFException
at
org.eclipse.pde.internal.build.tasks.BrandTask.execute(Brand Task.java:48)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)

* So, on the hunch that this is related to branding, I delete the name of
my Program Launcher in .Product file and rerun the build.
* Now it gets down into the Director phase of build. This fails until I
add the following plugins to my Feature:
org.apache.commons.httpclient
org.apache.commons.codec.binary
org.eclipse.ecf
org.eclipse.ecf.filetransfer
org.eclipse.ecf.identity
org.eclipse.ecf.provider.filetransfer
org.eclipse.ecf.provider.filetransfer.httpclient
org.eclipse.ecf.provider.filetransfer.httpclient.ssl
org.eclipse.ecf.provider.filetransfer.ssl
org.eclipse.ecf.ssl

* Now my build seems to complete, although there is no eclipse.exe in the
package.

* Next, I Import org.eclipse.equinox.executable into my workspace and add
it to the Product Feature list. PDE does not seem to find this feature if
in the Product Feature list alone.

* After build, eclipse.exe is now finally in the package!
* I still can't seem to figure out how to set custom Program Launcher
name, though.
Previous Topic:Partial success of PDE build on 3.5M6
Next Topic:swt paintevents on osx
Goto Forum:
  


Current Time: Thu Jun 17 18:53:59 GMT 2021

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

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

Back to the top