Hello, Well, it's not really a feature request, not really a bug... But anyway, here it goes : I was wondering why I had never had any history for my Java classes. And finally, I know why. It's simply because I did not include my source tree in my project path. So there is a project path and a source path, respectively with a project pane and a source pane. My question is the following, why my classes in my source tree aren't versionned and stored in my local VCS ? I think it's clever to have in my project path all the stuffs related to my Web app (including JSPs), and in my source path everything related to my source files (Servlets, Beans, etc...). Isn't it the way it should be ? If it's not, why is there a source pane if we have to include the sources in the project path ? Why should I include my source tree in my project path (in order to have it version controlled) when it's already in my source path ? Maybe some options or checkboxes should be included in the configuration pane, like : source tree versionning, project tree versionning... etc... Following the same idea, it'd be cool if we could exclude certain folder from being versionned. It was already in a previous request I made regarding compilation, finding usages, refactoring : we should be able to hide/unhide sub-folders from the project and/or source pane. Thus, we could have a fine-grained way of choosing the files that need to be compiled, searched for usages, refactored, AND versionned or not.
Guillaume _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
