Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 120371

Summary:	[model] Spurious empty package if source folder is creating using exclusion filters
Product:	[Eclipse Project] JDT	Reporter:	Tobias Widmer <tobias_widmer>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	martinae
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:	stalebug

Description Tobias Widmer

2005-12-12 10:23:17 EST

N20051211-0010

Steps to reproduce:
- Enable auto build
- Create new Java project, use project folder as source and output folder
- Create new source folder, use exclusion filters to solve nesting
- Create new package in source folder

-> Same package is rendered both in the project folder and the source folder
-> Package is actually not package on classpath, but subfolder of the output folder (in this case the project folder)

Comment 1 Martin Aeschlimann

2005-12-12 15:32:49 EST

reproduced, the package really is created at two locations (not a view problem).
We're using root.createPackageFragment(packName, true, monitor) to create the package.

Comment 2 Jerome Lanneluc

2005-12-13 05:28:07 EST

I cannot reproduce using I20051213-0010. Please reopen if you have more details.

Comment 3 Tobias Widmer

2005-12-13 05:36:12 EST

Strange enough, the option to update the exclusion filters is disabled in I20051213-0010.
Martin, is this by design? The scenario mentioned in comment 0 cannot be reproduced anymore.

Comment 4 Jerome Lanneluc

2005-12-13 05:43:44 EST

Actually, I was able to use the option to update the exclusion filters in the new source folder wizard. 
I said I could not reproduce because when I created the package 'x.y', it appeared  below the source folder only in the Package Explorer, and no empty package appeared.

Comment 5 Martin Aeschlimann

2005-12-13 05:51:24 EST

No, there hasn't been any change. I can still reproduce it:

1. In the toolbar, invoke the 'New Java project' item
2. Enter a name 'P', Select 'Use project as root...', press OK
3. Select 'P' in Project explorer, properties, configure
4. On the Java Build Path page go to the source tab, Add Folder, enter name 'x'
   Press OK, on the dialog (want to remove project...) press 'No' 
5. Select folder 'x' in package explorer, in the toolbar invoke 'New Java Package'
6. Enter package name 'a.b', press OK
7. Now have a look at the package explorer (and the resource navigator):
   They both contain elements P/a/b and P/x/a/b.

Comment 6 Jerome Lanneluc

2005-12-13 07:48:43 EST

To reproduce, you must have autobuild on.
The extra empty package is in the output folder of the project.
Need to see if this can/should be filtered out.

Comment 7 Jerome Lanneluc

2007-06-22 04:46:42 EDT

Reproduced using 3.3RC4

Comment 8 Jerome Lanneluc

2008-05-07 12:29:32 EDT

We ran out of time. Deferring post 3.4

Comment 9 Eclipse Genie

2020-03-13 10:24:55 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.