Summary: | Should not complain about package for empty units | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | john.arthorne |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2002-08-14 09:02:59 EDT
This is a valid usecase, will turn off the check for empty units. We might also consider turning this error into a configurable problem (error/warning/ignore), but this might induce confusion down the road. Note that our batch compiler will behave like javac, but the check occurs when the Eclipse Java builder is triggered so as to maintain the source tree consistency (and allow incremental compilation to perform in a predictable fashion). Backporting to 2.0.1. We will only avoid complaining for empty units (contents length == 0). If containing one space, we will start complaining. Verified Verified. Testing in 2.0.1 build 20020821, I noticed it now does NOT complain even if the file contains only whitespace. This is different behaviour from Philippe's last comment. John, I am observing the behavior I described in my previous comment. As soon as a space is added, the package error is reported. Can you provide steps to reproduce what you are seeing ? Create a .java file in the default package. If it contains only whitespace there are no build problems reported. Verified in 2.1 M1 |