Community
Participate
Working Groups
Currently when Exporting Preferences from the workbench user has the option to export All preferences, or to Choose specific preferences to export. User can export Installed JREs, or if Window->Preferences->General->Keys are modified, these also appear in the options to export these preferences. However, as an example, if user modifies Window->Preferences->Java->Build Path->Classpath Variables, these do NOT appear in the option to export specific preferences. Why are certain preferences available to export and not others? Would like to request that ANY preference changed would appear in this dialog box.
Window->Preferences->Java->Build Path->Classpath Variables needs to define a preference transfer for this.
Moving to JDT/UI
Can you give more background why you want to export classpath variables only? There has been no with for this so far, I believe.
(In reply to comment #3) > Can you give more background why you want to export classpath variables only? > There has been no with for this so far, I believe. The intention is to be able to create an export file with only specific preferences selected, classpath variables being just an example. The reasoning is that we could then export a preferences file with just company or department standards included. That file could then be used as a template for all workspaces created by developers, and it would only overlay the prefences we wished to standardize on (all other preferences could remain intact if the file prefs were loaded into an already user-modified set of preferences).
If we would categorize all options offered by the Java tooling, we would end up with 20-30 sections or more and we would still get requests for more fine grained sections... That's why I'd rather concentrate on sections for the options that are useful and requested. Is export classpath variables really one of these?
If you still need this then please explain in more detail why this would be useful.
The addition of just classpath variables to the individual export ability is not a high priority for us. The original intent of the posting was based on the fact that the user interface made it seem like we should be able to export any set of individual preferences (perhaps grouped by the top level nodes in the preferences window). If there was a generic way to implement the ability to export these sets of preferences that would be quite useful, but if this involves manually implementing a solution for each subset then I would agree that "WONTFIX" is the correct choice. Thanks for looking into this.
>If there was a generic way to implement the ability to >export these sets of preferences that would be quite useful Unfortunately there's not such solution because originally the preference were not modeled/declared. I've added two new transfers, one for compiler preferences and one for Java appearance preferences.
