Bug 6461 - NewBuilder - doesn't detect incorrectly located compilation units
Summary: NewBuilder - doesn't detect incorrectly located compilation units
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-30 09:18 EST by Philipe Mulet CLA
Modified: 2002-01-14 11:50 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2001-11-30 09:18:20 EST
Build 20011127+ latest JDTCORE
---------------

(1) Define project with source folder 'src'

P
+- src
    +- X.java with content:  [class X {}]

+- bin

(2) Full build of P
  Notice that P/bin/X.class was created ok.

(3) Edit X.java and add package statement [package p1;]

(4) Incremental build of P
  Notice that:
   a) No complaint was issued about the fact X.java is located incorrectly
       with respect to its package statement.
   b) P/bin/X.class is still there (wrong)
       though P/bin/p1/X.class was added (ok)
Comment 1 Philipe Mulet CLA 2001-12-03 09:23:49 EST
Fixed by adding notion of expected package name on compilation units.