Bugzilla – Full Text Bug Listing
| Summary: | Comments past end-of-class breaks New Java Project | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Andrew Hayden <aexx> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M4 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
User error. D'oh. |
When creating a new Java Project using a source tree that already exists and is not yet under Eclipse control (e.g., a project checked out using command-line CVS that you want to then import into Eclipse, or any other project where the source tree is not currently in Eclipse control), the "New Java Project" will break when you choose to use the pre-existing directory as the workspace if it is the case that any .java file in the directory structure contains a single- line comment immediately following the closing brace of the class definition. Example of a java file that will break the New Project functionality: file called MyClass.java: ****START OF FILE**** package org.eclipse.MyClass; public class MyClass extends Object { //A fun class with nothing in it that breaks Eclipse }//A comment outside of the class definition ****END OF FILE****