+1 for all > 3. External Resources. Often, a project will carry along resources that > should not be made global. Especially when you use a External Entity to handle an include in ant (since we have a discussion going on about it right now;-). These includes are project dependents.
This discussion allows me to recall another feature request (when are we going to have a defect tracking system, I wonder. It would reduce the redundant chatter...patience patience): The possibility to specify settings at multiple levels (user, project,global). Let's keep External Resources as an example: you might have global ones like global dtds. These should not go to the project level. They would go at the global level. The ant includes would go to the project level. Going further you might want to have a user specific override for you only that override some project settings. Project settings would override the global settings. Obviously it is an additive operation: the External Resources IDEA would get back would be the sum of all level External Resources defined. The previous overriding behavior would take care of duplicates. Jacques _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
