RE: [Subclipse-users] Identify subfolder of Eclipse project as working copy
From: Michael Schechter <mschechter_at_national.aaa.com>
Date: Mon, 22 Feb 2010 10:51:14 -0500
Nathan,
Sorry if I was unclear - we don't commit the workspace metadata. All we commit is an empty directory for developers to put the workspace in (that means that we don't have issues when working on multiple branches).
Things like configuration can be exported and committed separately (that even includes code formatting rules). My only recommendation is that you always sort the preferences file (simple text sort) prior to commit, as that way you can easily keep track of changes.
Hope this helps!
Michael Schechter
-----Original Message-----
Thanks for the suggestion Michael.
I haven't recently experimented much with Eclipse's import feature, after some bad experiences with it under Eclipse 2.x. I think I may be able to work that into a solution, though.
Personally, I dislike committing workspace metadata, though I can see its appeal in a larger organization where enforcing consistency of development platforms would be more of an issue (e.g., ensuring each developer of a project has certain Eclipse warnings turned on).
Just FYI, the "multiple-IDE" configuration is because I find one IDE to be better than others for working on certain aspects of a system. Even aside from that, however, I like to have available the cumulative analysis capabilities of each IDE, since the issues discovered by each do not entirely overlap.
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
This communication (including all attachments) is intended solely for
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
|
This is an archived mail posted to the Subclipse Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.