Bug 576543 - An error occurred while creating project
Summary: An error occurred while creating project
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.20   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-09 10:48 EDT by dev guy CLA
Modified: 2023-10-02 12:45 EDT (History)
1 user (show)

See Also:

Attachments
log file (702.51 KB, text/x-log)
2021-10-11 19:28 EDT, dev guy CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dev guy CLA 2021-10-09 10:48:51 EDT 
Press CTRL+N, then selecting "Java Project" I get an error dialog popup after the "Create Java Project" wizard is show.

The popup error message say, 

"An error occurred while creating project. Check log for details"
"Path for project must have only one segment"

However if I create a new project by selected "File -> New -> Java Project" the wizard comes up with no error and I am able to create a new Project in my workspace.





-- Configuration Details --
Product: Eclipse IDE 4.21.0.20210910-1200 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.platform 4.21.0.v20210906-0842
Comment 1 Rolf Theunissen CLA 2021-10-11 04:40:41 EDT 
I expect that the CTRL-N wizard does not allow to create projects in a nested folder, hence the 'Path for project must have only one segment'.

Could you attach the full log message from the .log file or the error view?

Moving to JDT, for further analysis.
Comment 2 dev guy CLA 2021-10-11 19:28:05 EDT 
Created attachment 287295 [details]
log file

Hi attached .log file, after reproducing the error again.

Here is a video showing the problem: https://www.youtube.com/watch?v=W4jCuCiCMlg
Comment 3 Eclipse Genie CLA 2023-10-02 12:45:20 EDT 
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.