On 3/20/07, Mark Phippard <email@example.com> wrote:
> I would like to be able to store the Eclipse-specific IDE files in the SVN
> repository. This makes checkout easier and allows for things like storing
> code formatting preferences in the repository so that Eclipse users have
> things work out of the box.
> I know the reluctance to doing stuff like this, so the idea I had was to
> create a folder under the"developer-resources" folder of the repository for
> this. It would keep it out of trunk and I would just use the svn:externals
> feature to pull the trunk code in on checkout. So an Eclipse user could do
> a checkout from this folder and it would give them everything all setup out
> of the box and ready to go.
> This would also make it easy to see what exactly the Eclipse-specific
> files are and possibly let them live in trunk later if they do not look too
> onerous to everyone.
Today's crowd on IRC seems to prefer this original idea, rather than put
files in trunk. So I have attached a patch that is more specific in terms
of what I am proposing. Based on IRC discussions, I have altered this a
little. Instead of using svn:externals to pull in the Subversion code, I
added an empty folder named "src". I would include a README file, that is
not in the patch that would instruct the user to use the switch command to
switch src to trunk or the branch of their choice.
The patch is adding a new folder named eclipse-project to the
developer-resources folder off the root of the repository. This folder
contains the Eclipse project files. A user could checkout this folder in
Eclipse, then use the switch option inside Eclipse to pull in the source
code. I cannot test this until the files are in the repository, so I may
have to tweak a few things after the initial commit. Conceptually it should
work though and using switch has benefits over externals, not the least of
which is making it easy to change between trunk and a branch.
Received on Wed Mar 21 17:58:52 2007
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com