Community
Participate
Working Groups
Created attachment 271444 [details] ErrorMessage I can't Export my Project (Main : in Class : Server), in the Image is the ErrorMessage. But I can run/debug these LaunchConfiguration without any problems. I have read many many posts to this Problem, but the solution was not there. I hope you can help me
New Gerrit change created: https://git.eclipse.org/r/111589
Anything in the log file? (In reply to Eclipse Genie from comment #1) > New Gerrit change created: https://git.eclipse.org/r/111589 This doesn't look like it belongs to this bug.
Sorry, the change referenced the wrong bug number. Fixed commit message.
Question: You are trying to export an executable Jar? If yes, would the launch config you are using as a reference execute without errors if you run it from the main menu? The error indicates that the launch config is corrupt.
Sorry, you already mentioned that you could execute it.
New Gerrit change created: https://git.eclipse.org/r/141265
The problem with the launch configuration which has a reference project is either deleted or closed. I think we need to control the launch configurations in combo based on preference settings. I submitted initial commit here https://git.eclipse.org/r/141265 There are API restriction errors. Need to fix it either change the severity level or contributing in debug plugin.
Is this still an issue ? Are there more detailed steps to reproduce because I'm not able to. I create 2 projects, where one is on the classpath/module path of the other under the projects tab of the build path. If I attempt to close/delete the project being depended upon I'm not able to run it and even the launch configuration states the issue. On the other hand, I do notice that I'm able to create a runnable jar with/without the patch referenced here, even when the project being depended upon is closed/deleted.
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.