For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 3 voices, and was last updated 22 years ago by
.
-
Posts
-
My WebRoot/WEB-INF/classes folder is hidden from the package explorer.
What do I need to do in order to display it’s contents ?win2k, 3.0m6, 3.7rc2
Well, the Package Explorer view is really for looking at source, not compiled products. I thought there was a way to modify the filtering to do what you’re looking for, but I couldn’t find it. If you use the Navigator view, however, you should be able to see what you like.
@scott wrote:
Well, the Package Explorer view is really for looking at source, not compiled products.
The classes folder is also an easy place to store properties, config files and other resources needed by the webapp.
I guess for now I’ll keep using the navigator, but if you could get the package explorer functional, that’d be great !
ivar,
The preferred practice is to keep you properties files in your source folder tree, and when the Eclipse builder runs, it copies them into your classes directory. When they are in your src tree you can see them and click on them fine in Package View (for example, the Application.properties file for most Struts programs)also, as NOP has pointed out before, the reasoning behind not manually putting your properties files in your classes folder is because Eclipse cleans out that dir before a build, which will cause your properties files to get erased.
@support-rkalla wrote:
The preferred practice is to keep you properties files in your source folder tree, and when the Eclipse builder runs, it copies them into your classes directory. When they are in your src tree you can see them and click on them fine in Package View (for example, the Application.properties file for most Struts programs)
Two main problems with this:
1- Our directory structure (in version control) has already been decided. It would cause much pain all around if I were to suggest a change.
2- Some of our properties /configs are dynamically reloaded. Having them copied would mean any changes would not affect the version control working copy (and lead to confusion, or at least the likelyhood that I’d forget to copy the files over to the working repository..)@support-rkalla wrote:
also, as NOP has pointed out before, the reasoning behind not manually putting your properties files in your classes folder is because Eclipse cleans out that dir before a build, which will cause your properties files to get erased.
I’ve turned off the ‘clean before build’ option. If I really need to clean it out, it’s trivial to delete the ‘ca’ directory (all our source is in a package that starts with .ca )
all I want ( in this post anyway 😈 ) is genuitec to make hiding the ‘classes’ folder optional..
ivar,
The functionality you are requesting is imposed by Eclipse, not the MyEclipse product. Please see the following report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=16528Unfortunately it seems the Eclipse team doesn’t plan on allowing output folder to be viewed any time soon. You can certainly file a request for the 3.0 release and it might make it in. I know IntelliJ offers functionality like this in the form of a list of “folders to hide”. You can simply remove your output folder from the hidden list, and then it is shown.
@support-rkalla wrote:
ivar,
The functionality you are requesting is imposed by Eclipse, not the MyEclipse product. Please see the following report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=16528wow. thanks for the due diligence ! I’ll see what I can do to get my way 🙂 but the bug belongs to erich gamma, so I doubt I’d hold much influence..
