Bug 544151 - A problem occured while invoking the director
Summary: A problem occured while invoking the director
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 blocker with 4 votes (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-05 13:59 EST by Kenneth Evans CLA
Modified: 2024-01-15 04:07 EST (History)
12 users (show)

See Also:


Attachments
Sample maven build of an RCP project (429.52 KB, application/zip)
2022-01-24 11:27 EST, Ralph Bosson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Evans CLA 2019-02-05 13:59:51 EST
I have an RCP application that was developed some time ago.  It has had only minor changes for some time, primarily the Eclipse version changing.  It runs OK in the Workbench but currently does not deploy.  Validate plug-ins in the run configuration is successful.  Not deploying is an ongoing problem with each Eclipse version, and I can usually fix the problem by adding dependencies that Eclipse shows as unused, see #310861

This is a new problem, and I have no idea how to fix it.  Deploy fails.

This is a stopper for me.

These are the Details for the Problem Occurred dialog that results from Eclipse Product Export Wizard:
C:\eclipseWorkspaces\RCP\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:90: The following error occurred while executing this line:
C:\eclipseWorkspaces\RCP\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:698: The following error occurred while executing this line:
C:\Users\evans\.p2\pool\plugins\org.eclipse.pde.build_3.10.200.v20181008-0641\scripts\genericTargets.xml:240: A problem occured while invoking the director.
The following error occurred while executing this line:
C:\eclipseWorkspaces\RCP\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:698: The following error occurred while executing this line:
C:\Users\evans\.p2\pool\plugins\org.eclipse.pde.build_3.10.200.v20181008-0641\scripts\genericTargets.xml:240: A problem occured while invoking the director.
Comment 1 Teresa Noviello CLA 2019-04-03 04:58:54 EDT
Are there news on this?
I have the same problem
C:\Users\user\eclipse-workspace\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:89: 
The following error occurred while executing this line:
C:\Users\user\eclipse-workspace\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:142: 
The following error occurred while executing this line:
C:\Users\user\.p2\pool\plugins\org.eclipse.pde.build_3.10.300.v20190305-0856\scripts\genericTargets.xml:240: 
A problem occurred while invoking the director.
The following error occurred while executing this line:
C:\Users\user\eclipse-workspace\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:142: 
The following error occurred while executing this line:
C:\Users\user\.p2\pool\plugins\org.eclipse.pde.build_3.10.300.v20190305-0856\scripts\genericTargets.xml:240: A problem occured while invoking the director.
Comment 2 Enver Stambouli CLA 2019-04-05 11:18:53 EDT
new bug opened 546019
Comment 3 Vikas Chandra CLA 2020-03-31 04:41:15 EDT
Can you try https://bugs.eclipse.org/bugs/show_bug.cgi?id=546019#c7
Comment 4 Kenneth Evans CLA 2020-03-31 09:33:43 EDT
I got it working back at the time of the incident.  The solution involved getting rid of all Eclipse help use and implementing my own web page as well as other trial and error.

This is an ongoing problem that happens with each Eclipse update. You get something that works just fine in Eclipse but which will not deploy.  In order to deploy you need dependencies that that are not added by "add required dependencies" and that are marked as not needed when added manually. This is in addition to the errors like this that just say the deploy failed, but with little information and no way to fix.  And with no help for the support incidences.

It is a nightmare. I have moved all but two of my RCP programs to other platforms or abandoned them.  These would be a significant effort to convert to a different UI and I don't have the time.
Comment 5 Kenneth Evans CLA 2020-09-26 15:01:28 EDT
It happened again.  Again I have no clue how to fix it. See Bug #567394 for updated information for Eclipse 2020-09.
Comment 6 Pablo Beltrán CLA 2020-12-30 16:41:07 EST
I've read from the mentioned bugs that this is related to Java 11. IMHO, it's not.

I stumbled with this bug on Eclipse 2020-09 and Java 11. Then I moved the product (RAP,  not RPC) to Eclipse 2020-06 and Java 8 and the problem still persists whereas the rest of the RCP examples work fine (they can be exported with a p2 self-hosted repository). So, the problem can be reproduced regardless of the Eclipse and JVM versions and it is dependent on the product configuration.
Comment 7 Kenneth Evans CLA 2020-12-30 19:01:58 EST
No, I also do not think it is owing to Java 11. The issue reported here was not even using Java 11. And in both this case and the newer one, which IS using Java 11, the product runs fine in the workbench. It's hard to see how it could be a problem with Java 11, itself.

That it works in the Workbench should indicate it is probably not a problem with the project configuration either.

It is almost surely a problem with the deployment logic. It could easily be that logic is not working correctly with Java 11. (There would have to be the caveat "in some cases" because I have another RCP project that has been converted to Java 11 and which does deploy properly.)

In the best of all possible worlds, a project that runs in the workbench should deploy and run. If there is an issue, it should be reported during deployment. In the best of all possible worlds someone with expertise in the deployment logic would look at these continuing issues.
Comment 8 Jonathan Masters CLA 2021-03-17 23:27:29 EDT
I have the same problem. What I can add is that it duplicates on Win10 and OSX. These export problems have been dogging me for several years and I have yet to find a solution. It is very disappointing to put effort into something that works on workbench and is very difficult to deploy.
Comment 9 Jonathan Masters CLA 2021-03-17 23:52:54 EDT
FWIW. I can get a build that runs if I don export a P2 repository. Which gets me by for now.
Comment 10 Jonathan Masters CLA 2021-03-17 23:53:16 EDT
FWIW. I can get a build that runs if I don't export a P2 repository. Which gets me by for now.
Comment 11 Ralph Bosson CLA 2021-06-03 15:18:24 EDT
I have feature based plugin project that deployed without issue for both OS X and Windows Java 1.8. Development environment Eclipse 4.4.2, OS X 10.15.7. When this product was installed on Big Sur problems where presented. I rebased the product to Java 11 development platform Eclipse 2021-03 (4.19.0) in hopes of address the issues. The only change required was the inclusion of JAXB as a fragment. The product launches without issue from the feature.product. I am receiving the following error when attempting an Export/Build using the following parameters: 
Allow for binary cycles in target platform
Generate p2 repository
Export for Multi-platform (OS X, Windows)

ERROR:
/workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:90: The following error occurred while executing this line:

/workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:1859: The following error occurred while executing this line:

/rcp-2021-03/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.pde.build_3.10.1000.v20210130-0813/scripts/genericTargets.xml:240: A problem occured while invoking the director.

I am dead in the water on this, the ant script gives limited information. If the parameter Generate p2 repository is removed other build problems present themselves. I will create a separate bug report on those issues. Be well
Comment 12 Ralph Bosson CLA 2021-06-03 15:50:55 EDT
Additional the .metadata .log reports
!ENTRY org.eclipse.ant.core 4 1 2021-06-03 13:00:08.878
!MESSAGE /workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:90: The following error occurred while executing this line:
/workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:978: The following error occurred while executing this line:
/rcp-2021-03/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.pde.build_3.10.1000.v20210130-0813/scripts/genericTargets.xml:240: A problem occured while invoking the director.
!STACK 0
/workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:90: The following error occurred while executing this line:
/workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:978: The following error occurred while executing this line:
/rcp-2021-03/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.pde.build_3.10.1000.v20210130-0813/scripts/genericTargets.xml:240: A problem occured while invoking the director.
	at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:582)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:440)
	at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
	at jdk.internal.reflect.GeneratedMethodAccessor834.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
	at org.apache.tools.ant.Task.perform(Task.java:350)
	at org.apache.tools.ant.Target.execute(Target.java:449)
	at org.apache.tools.ant.Target.performTasks(Target.java:470)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:34)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
	at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:712)
	at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:532)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.ant.core.AntRunner.run(AntRunner.java:374)
	at org.eclipse.pde.internal.core.exports.FeatureExportOperation.runScript(FeatureExportOperation.java:472)
	at org.eclipse.pde.internal.core.exports.FeatureExportOperation.doExport(FeatureExportOperation.java:336)
	at org.eclipse.pde.internal.core.exports.ProductExportOperation.run(ProductExportOperation.java:134)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: /workspace/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.macosx.cocoa.x86_64.xml:978: The following error occurred while executing this line:
/rcp-2021-03/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.pde.build_3.10.1000.v20210130-0813/scripts/genericTargets.xml:240: A problem occured while invoking the director.
	at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:582)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:440)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
	at jdk.internal.reflect.GeneratedMethodAccessor834.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
	at org.apache.tools.ant.Task.perform(Task.java:350)
	at org.apache.tools.ant.Target.execute(Target.java:449)
	at org.apache.tools.ant.Target.performTasks(Target.java:470)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
	at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
	at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:32)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
	... 25 more
Caused by: /rcp-2021-03/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.pde.build_3.10.1000.v20210130-0813/scripts/genericTargets.xml:240: A problem occured while invoking the director.
	at org.eclipse.equinox.p2.director.app.ant.DirectorTask.execute(DirectorTask.java:97)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
	at jdk.internal.reflect.GeneratedMethodAccessor834.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
	at org.apache.tools.ant.Task.perform(Task.java:350)
	at org.apache.tools.ant.Target.execute(Target.java:449)
	at org.apache.tools.ant.Target.performTasks(Target.java:470)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
	at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
	at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:32)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
	... 38 more
Comment 13 Alfred Sterphone CLA 2021-07-12 21:44:04 EDT
(In reply to Jonathan Masters from comment #10)
> FWIW. I can get a build that runs if I don't export a P2 repository. Which
> gets me by for now.

How does your build run without a p2 directory?
Comment 14 Tom Studer CLA 2021-07-28 02:36:02 EDT
How to reproduce:

* Install the 2021-06 PDE/RCP Eclipse IDE (in my case on Windows 10 selecting JRE16). Then:
* New Plugin Project
** enter name, next
** "Create Rich Client Application": Yes, next
** Choose "Eclipse RCP Application", next
** Check "Create sample content". finish
* Run the product as Eclipse Application (starts fine)
* Now select the product definition file and use the Export wizard to export
** Provide a target directory name, otherwise click through the defaults of the wizard

--> 'Export Product' has encountered a problem: A problem occured while invoking the director.

I got the same results with a previous Eclipse release (I deleted that one but think it was the last from 2020)
Comment 15 Tim Schmid CLA 2022-01-12 02:39:49 EST
I have the same issue
Comment 16 Randall Becker CLA 2022-01-23 21:44:31 EST
RCP deployment in 2020-03 and 2021-09 is definitely not working, even with an RCP created using those instances. This is a blocker, not a trivial problem.
Comment 17 Phil Beauvoir CLA 2022-01-24 04:43:39 EST
But isn't PDE Build no longer supported? I thought that Tycho/Maven was the way to go now for RCP builds.
Comment 18 Alfred Sterphone CLA 2022-01-24 08:51:32 EST
(In reply to Phil Beauvoir from comment #17)
> But isn't PDE Build no longer supported? I thought that Tycho/Maven was the
> way to go now for RCP builds.

Even if this is true, there is no clear officially documented way to migrate from Eclipse 3.x PDE build to Tycho/Maven. I have spent hours trying and have gotten maybe 70% of the way there, but not all the way. Cobbling together bits and pieces from various wikis and tutorials.

If the .product "Export" is no longer supported, then the user experience should be updated to reflect as much. Further, migration to Tycho should be built in.
Comment 19 Ralph Bosson CLA 2022-01-24 11:27:39 EST
Created attachment 287885 [details]
Sample maven build of an RCP project
Comment 20 Ralph Bosson CLA 2022-01-24 11:30:35 EST
I have removed com.corgroup.maven.test-repository/target from the upload for brevity. Otherwise the I was able to use the 6 plugins to create a sample RCP product. Hope it helps
Comment 21 Eclipse Genie CLA 2024-01-15 04:07:31 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.