While starting to play with JDeveloper 10.1.3 preview, Andrej says:
I created a new workspace and a new project, and then I created one new file in this project: a file called config.cfg in a folder conf. The first thing i do in this new jdeveloper version, and immediately i seem to experience a bug or a misunderstanding on my part: the project doesn't show config.cfg. I've edited the working set (which shows the conf directory), i added a *.cfg pattern to the working set. I've also added the extension .cfg under File Types in the preferences windows, but nothing helps. Config.cfg is not displayed as part of my project...
It wasn't clear from Andrej's post whether he created his config directory containing the config.cfg file right inside the workspace directory (/yourapp/config/config.cfg), or else within the workspace's Java source directory (/yourapp/src/config/config.cfg). I suspect he did the latter, given that it didn't show up. Here I'll try to explain what's going on.
Here I've created both the top-level ./config/config.cfg file and a ./src/config/config.cfg file in a new application workspace, and I've used the View menu to show both the System Navigator and the Application Navigator. 
In the JDeveloper 10.1.3 preview, there are some new features that currently are only supported in the System Navigator, and not yet in the Application Navigator. One of these is the user-controllable package-folding level toolbar. You can use this to decide how many levels of package names should be shown as "flat" while the remaining levels show nested under those flat package names. Another is the Working Sets feature, where you can create one or more filters over the navigator to switch between filtered subsets of the files. The third is the ability to show libraries or not in the navigator (toggleable with another toolbar icon that looks like a book). The fourth is the ability to show or suppress the root directory folders in the different contents paths in the project (controlled by the toolbar icon that looks like a folder).
By default, the "./src" directory is configured as a root directory in the Java content of your project, and any Java sources that appears in that Java content path show up in the navigator.
In addition to the Java content for a project, there are other kinds of content that contribute to the project like general resources, offline database content, models, and web content. By default, there isn't any fixed directory for holding general resources like Andrej's config.cfg file in the top-level ./config directory of his workspace.
In the screenshot above, I've visited the project properties and gone to the Project Content section. I expanded it to show the "Resources" panel, and added the ./config directory as a root directory for resource-type content. The key difference between Java content and resource content is that Java gets compiled and it gets visualized in a package-structure. Resources on the other hand, have no build/compile semantics, and display in folder structure rather than package structure.
Send me an email if you can suggest how we can make this feature more easy to learn out of the box!
12:15:22 AM 
|
