| Summary: | META-INF directories shown as empty META-INF.* packages in J2EE Navigator | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Yen Lu <yenlu> |
| Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | daniel_megert, jeffliu, konstantin, markus.kell.r |
| Version: | 3.1.2 | ||
| Target Milestone: | 3.2 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Yen Lu
Added to 1.0.2 hotlist. Setting priority to P2, target to 1.0.2 M102 This is a problem with the base JDT Package Explorer as well. It looks like it is smart enough to not treat META-INF as a package, but not smart enough to ignore folders under META-INF. You can see this behavior with a standard Java project. 03/09 status meeting - John will investigate this bug. Hi, Has there been any investigation into this problem? Would it be possible to address in Eclipse 3.2? Thanks, Yen This bug is now removed from the WTP 1.0.2 hot list. It has been added to WTP's Callisto cross-project issues (bug 128412). We're getting a wrong Java model delta here:
Java Model[*]: {CHILDREN}
zzPlug[*]: {CHILDREN | CONTENT}
<project root>[*]: {CHILDREN}
META-INF.f5[+]: {}
ResourceDelta(/zzPlug/META-INF)[*]
The resource delta is fine, but the package fragment addition META-INF.f5[+] is wrong. Note that this only occurs if the project is used as source folder. Moving to JDT/Core.
Changed DeltaProcessor#elementType(IResource, int, int, RootInfo) to return a NON_JAVA_RESOURCE if the parent is a NON_JAVA_RESOURCE because of its name. Added regression test JavaElementDeltaTests#testAddFolderInNonJavaFolder() Verified for 3.2 M6 using build I20060329-0010. |