Plug-in dependencies for runtime workspaces is broken in Eclipse (Modeling) 2025-03 R on Windows

[maxkratz]

Hi,
I found a bug when using plug-in dependencies in runtime workspaces with Eclipse (Modeling) 2025-03 R on Windows. I opened an issue at the EMF repository but I was told this could be a PDE problem.

Copy paste from the other issue:

Bug description:

Normally, you can create a plug-in project in your development workspace and let it export some Java packages. The import and export of such projects are managed via the MANIFEST.MF file(s). On your runtime workspace, you can have other projects that have the projects of the development workspace as a dependency defined in their MANIFEST.MF. Eclipse should normally resolve the dependencies automatically and compile the project(s) within the runtime workspace correctly.

However, since updating to Eclipse Modeling 2025-03 R this seems to be broken on Windows-based systems only.

I documented it with a description and an MWE consisting of two Eclipse projects in this repository: https://github.com/maxkratz/eclipse-2025-03-runtime-bug-mwe

If this is not the right place to raise this issue, please let me know. I would happily get a pointer to the correct repository/mailing list, etc.
I appreciate any help you can provide.

[merks]

Is it possible that your launch configuration has a space in the name? I see that the existing logic is not properly decoding the %20 when converting the URL to a path pass to the File constructor:

I know there have been changes in other places to create well-formed URLs. A URL tolerates a space, a URI does not and throws an exception....

[maxkratz]

Is it possible that your launch configuration has a space in the name?

Yes, my home folder on my Windows systems contains a space: C:\Users\Maximilian Kratz\.... I will try to reproduce the issue with workspaces that do not have a space in their paths.

[maxkratz]

Is it possible that your launch configuration has a space in the name?

Yes, my home folder on my Windows systems contains a space: C:\Users\Maximilian Kratz\.... I will try to reproduce the issue with workspaces that do not have a space in their paths.

I've tested it again with both workspaces and both projects in C:\tmp (i.e., no space within the paths), but the problem persists.

[merks]

A space in the launch configuration name will also cause the problem. Anything which results in encoded characters in the -dev argument will cause the problem:

[merks]

I believe the problem to be fixed but PR that I've merged...

[maxkratz]

A space in the launch configuration name will also cause the problem. Anything which results in encoded characters in the -dev argument will cause the problem:

I believe I don't have any space characters in the respective paths, but I'm not completely sure about that.

I believe the problem to be fixed but PR that I've merged...

Is there a CI build of Eclipse that I can check out?

[merks]

Tomorrow's I-build will contain the fix:

https://download.eclipse.org/eclipse/downloads/index.html

Currently it's I20250326-1800 because the builds were broken...

[maxkratz]

Tomorrow's I-build will contain the fix:

https://download.eclipse.org/eclipse/downloads/index.html

Currently it's I20250326-1800 because the builds were broken...

Thank you for the link.

I tried to update a fresh copy of Eclipse Modeling Tools to the build I20250330-1800 but I did not get the dependencies of my MWE runtime project to work correctly.

What I did:

• Download a fresh Eclipse Modeling Tools, extract it, and start it.
• Go to Help -> Install New Software... -> paste the update site https://download.eclipse.org/eclipse/updates/4.36-I-builds/I20250330-1800
• Install all available packages
• Restart Eclipse
• Proceed with the testing as described in my MWE repository

Did I skip some steps or did I make a mistake?

Another question that came to my mind: will there be a new release of Eclipse 2025-03 R with the included PDE fix (you merged) or do we have to wait for Eclipse 2026-06 R?

[maxkratz]

What I did:

• Download a fresh Eclipse Modeling Tools, extract it, and start it.
• Go to Help -> Install New Software... -> paste the update site https://download.eclipse.org/eclipse/updates/4.36-I-builds/I20250330-1800
• Install all available packages
• Restart Eclipse
• Proceed with the testing as described in my MWE repository

Did I skip some steps or did I make a mistake?

Interestingly, I ran another round of updates in Eclipse (via Help -> Check for Updates), and now, all the errors are gone.

[laeubi]

will there be a new release of Eclipse 2025-03 R with the included PDE fix

No

do we have to wait for Eclipse 2026-06 R

No you can use the milestones repo https://download.eclipse.org/releases/milestone/ then you will get an M1 / M2 releases and so on. This is also a great way to report problems before the release and get them fixed soon.

[maxkratz]

will there be a new release of Eclipse 2025-03 R with the included PDE fix

No

do we have to wait for Eclipse 2026-06 R

No you can use the milestones repo https://download.eclipse.org/releases/milestone/ then you will get an M1 / M2 releases and so on. This is also a great way to report problems before the release and get them fixed soon.

Thank you for your fast response.

Are the milestone releases stable in the sense that we can roll them out for our users?