Community
Participate
Working Groups
Build Identifier: 20120216-1857 I now get an error when I try to use the "New Java Class" wizard. I have been using Eclipse for years and have never seen this before. It was working fine yesterday, but it seemed to stop working after I updated my TestNG plugin (which Eclipse promoted me to do per it's auto-update settings). Reproducible: Sometimes Steps to Reproduce: 1. I bring up the "New Java Class" wizard by right clicking on a package. 2. I fill out the name of the new Java class, and make no further changes to the default option. 3. when I click "Finish" I get the following dialog: > Creation of element failed. > org.eclipse.jdt.internal.core.search.matching.TypeDeclarationPattern 4. When I click "Ok" I'm returned to the "New Java Class" dialog. I notice that a Java file has been created with the appropriate name, but instead of package and a skeleton class definition, this file is empty.
s/promoted/prompted
Ok, restarting Eclipse again resolved this issue.
(In reply to comment #0) > > Creation of element failed. > > org.eclipse.jdt.internal.core.search.matching.TypeDeclarationPattern Could you please provide the whole stack trace ? This can help to identify what is not working. Once you restart, does it always work?
> Could you please provide the whole stack trace ? This can help to identify what is not working. Unfortunately it was not provided in the error dialog, and I didn't think to check my console. Sorry. > Once you restart, does it always work? So far, so good.
There could be some information in <workspace-folder>/.metadata/.log. Can you please give that?
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.
Moving
