Bug 130982 - META-INF directories shown as empty META-INF.* packages in J2EE Navigator
Summary: META-INF directories shown as empty META-INF.* packages in J2EE Navigator
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1.2   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-08 16:11 EST by Yen Lu CLA
Modified: 2006-03-29 03:20 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yen Lu CLA 2006-03-08 16:11:18 EST 
when we create an EJB project and then create some non-Java folders and files under META-INF, the J2EE Navigator shows the directories as empty Java packages which are misleading users into thinking additional directories are being auto-created. For example, we create a wsdl folder under META-INF, we see META-INF.wsdl as an empty package.

John Lanuti is aware of this problem.
Comment 1 Jeffrey Liu CLA 2006-03-09 03:42:11 EST 
Added to 1.0.2 hotlist. Setting priority to P2, target to 1.0.2 M102
Comment 2 Konstantin Komissarchik CLA 2006-03-09 21:26:14 EST 
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.
Comment 3 Jeffrey Liu CLA 2006-03-10 11:02:00 EST 
03/09 status meeting - John will investigate this bug.
Comment 4 Yen Lu CLA 2006-03-16 12:59:02 EST 
Hi,

Has there been any investigation into this problem? Would it be possible to
address in Eclipse 3.2?

Thanks,
Yen
Comment 5 Jeffrey Liu CLA 2006-03-17 10:34:11 EST 
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).
Comment 6 Markus Keller CLA 2006-03-17 11:30:19 EST 
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.
Comment 7 Jerome Lanneluc CLA 2006-03-28 08:01:07 EST 
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()
Comment 8 Maxime Daniel CLA 2006-03-29 03:20:16 EST 
Verified for 3.2 M6 using build I20060329-0010.