Community
Participate
Working Groups
As a team, we have a standard around the compiler settings. Everything else though is configurable for the developer, but we want to be sure we all use the same settings for warnings/errors. I want to be able to export just those settings so that my team members can import those. As it is, I have to export the entire set of preferences, edit them by hand to sort them and then strip out everything except for the compiler settings. I'm not even sure that approach is safe.
You can set the compiler's preferences per project and commit them to CVS. Then any developer that checked them out would use the project's specific preferences. Ok to close?
We do not use CVS. We use Rational ClearCase, which doesn't have the support you're referring to. Besides, I wouldn't think you would want to count on having the SCM be the mechanism by which teams can share compiler settings. When I go to File->Export->Preferences, I'd like to see an option there for "compiler settings".
Moving to JDT/UI
*** Bug 202276 has been marked as a duplicate of this bug. ***
*** Bug 207949 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > You can set the compiler's preferences per project and commit them to CVS. If I click File > Export > Preferences and export all preferences, I find absolute paths in that file. Is this related to bug 57732? Then it would be unusable for sharing.
bug 57732 is not related to this. bug 57732 is about '.classpath.' But you're right, File > Export > Preferences will export all settings and some contain platform specific paths, which is bad for sharing. But you should try project specific settings: Go to the project's property page to enable this. This will create a file .settings/org.eclipse.jdt.core.prefs in your project and therfore part of the files that are shared by a team provider. I don't see why wouldn't that work with ClearCase?
As mentioned in the original bug report, we have a standard around compiler settings, but everything else we want to leave configurable. If I export MY settings (project specific or not), and other import them, then they're getting all my other settings. Today I have to export all, and then whittle out everything except for compiler settings to get where we want to go.
It would sure be nice if settings were better categorized but today it seems there are very few categories and everything else falls into another "other" category that includes effectively all uncategorized things, many of which are specific to the installation location and hence aren't really suitable to be exported at all... If I have 100 project's having project specific settings duplicated across a 100 projects is far from ideal as well...
I'm afraid I have to retarget this to 3.5 as there was no progress on bug 208564. A fix for bug 208564 is required as we can't and don't want to enumerate all compiler options in the plugin.xml. There too many.
(In reply to comment #8) > As mentioned in the original bug report, we have a standard around compiler > settings, but everything else we want to leave configurable. If I export MY > settings (project specific or not), and other import them, then they're getting > all my other settings. Today I have to export all, and then whittle out > everything except for compiler settings to get where we want to go. Project-specific settings already allow you to be selective about the things that are shared. You still have not indicated why project-specific settings will not meet your needs. I understand the desire to be more selective in workspace preferences export/import, but I think that is a more broad request (and a lot of work, apparently) and it seems obvious that project-specific settings is the answer to the original request in this bug. Relying on workspace-wide settings is not very reliable anyway, for several reasons. As for synchronizing the project-specific settings across a large set of projects, I agree with Ed that there is pain there. But I think that can be addressed with better tool support. I'm looking for an existing bug report on that topic and will enter a new one if I can't find anything.
Bug 194414 talks about syncing settings across many projects.
Sorry, still need bug 208564 for this. Moving to 3.6.
Fixed in HEAD. Available in builds > N20090930-2000.
Verified in I20091026-1442 Able to export/import workspace specific compiler settings.
.
*** Bug 240798 has been marked as a duplicate of this bug. ***
*** Bug 121261 has been marked as a duplicate of this bug. ***
