Hi Folke.
In my opinion, if you want to get people to use Eclipse instead of IDEA, you
SHOULD commit the eclipse project settings so that people can just check out
the "project" and have everything set up for that project, rather than
having to set up the project preferences every time they check it out, etc.
We have a plugin based application and hence have many "projects" to work
with, but not all at once and not all the time, so being able to check out a
project and have the classpath already set up, etc, makes life MUCH easier.
Repetition is the killer of motivation when transitioning people to a new
tool, so if you can do things to reduce that you stand a much better chance
of getting others to follow to Eclipse.
In direct response to your request though, from memory, doing the Share
Project just creates the projects directory in the repository. You then do
a commit to commit the sources, so you can just uncheck the eclipse files
before hitting OK.
Just my 2c.
Greg.
Ps. We keep everything under revision, resources, sources, images, etc.
anything that is part of our application, but particularly anything that
might change between deployments so we can reproduce an installation exactly
at any stage (might want to demonstrate an old release, or need it for
reproducing an old bug, or whatever).
-----Original Message-----
From: Folke Lemaitre [mailto:folke@landc.be]
Sent: Thursday, 19 January 2006 7:38 PM
To: users@subclipse.tigris.org
Subject: [Subclipse-users] Feature Request: Share Directory
Hi,
I don't know whether this is the right place for feature requests, but
here is my feature request:
At the moment it is not possible to only share some sub directories from
an eclipse project, though that would be really a cool feature.
The reason I really need this is because I don't want to have the
eclipse specific project settings on subversion, I only want the real
program sources there.
For example:
*Svn Layout:*
http://somserver/svn/trunk/project1
*Eclipse project layout:*
/src -> http://somserver/svn/trunk/project1
/teststuff
/data
some_test_output_I_dont_want_on_subversion.txt
.project
.classpath
Being able to share directories would also allow eclipse project layout
such as:
/src -> http://somserver/svn/trunk/project1
/othersrc -> http://somserver/svn/trunk/proj3
/data -> http://dataserver/svn/trunk/data
some_test_output_I_dont_want_on_subversion.txt
.project
.classpath
The reasons that I dont want to put the complete eclipse project folder
into subversion are:
* Not everybody from our team uses eclipse (some use Idea,...)
* Personally I prefer to have only pure sources under source control
At the moment I use some kind of work around:
* I create an eclipse src project containing / ->
http://somserver/svn/trunk/project1
* I create an eclipse bin project that is initially empty and refers
to the src project
* I create run configurations in the src project, and change their
project to the bin project.
This works for me, but is not ideal, specially for people I want to
convince to start developing in Eclipse instead of in IntelliJ IDEA :-)
Please give me some comments on whether this sounds like a good idea or
not (and maybe a place where I can submit feature requests)
Greetings,
Folke
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jan 23 00:33:46 2006