This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 53957 - non java files in Eproject
Summary: non java files in Eproject
Alias: None
Product: projects
Classification: Unclassified
Component: Eclipse project importer (show other bugs)
Version: 4.x
Hardware: Other Other
: P4 blocker (vote)
Assignee: Jesse Glick
Depends on: 140344
  Show dependency tree
Reported: 2005-01-25 13:33 UTC by Pavel Rehak
Modified: 2008-07-30 22:53 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Rehak 2005-01-25 13:33:53 UTC
In eclipse you're able explicitly bind non-java 
files with your project and they are visible in 
project structure.
It can be a bit confusing for NB users if such a 
files are not imported as part of NB project 
(altought such a project is compilable after 
import. i didn't find single usecase which could 
damage import from enclipse in meaning of non-

In general NB doesn't support binding non-java 
files with the project - its just for your 
Comment 1 David Konecny 2008-06-16 01:07:54 UTC
Could you please provide an example Eclipse project or just describe how to create one? I'm not sure what you mean by
"bind non-java files with your project". Thanks, David.
Comment 2 Jesse Glick 2008-07-30 22:53:47 UTC
Possibly the reporter meant that files outside a src/ dir but inside the project dir should be visible. But this is true
even when importing into NB, if you create the NB metadata inside the Eclipse project.

For the case that you create NB metadata externally, this is really a special case of issue #140344.