|Re: Best approach to Eclipse for shared projects? [message #1403991 is a reply to message #1403777]
|Tue, 29 July 2014 01:51
| David Wegener
Registered: July 2009
On 07/27/2014 11:10 AM, Christian Convey wrote:
> I'm pretty new to Eclipse, and completely new to Eclipse+Git as a
> Can anyone tell me if there's a known-good solution to the following
> I'm developing some Java code that I want to store on github. I want
> that code to be easily buildable by other persons who aren't using
> Eclipse. But I'd like to be able to use Eclipse when I'm working on
> that code.
> My concern is that if I don't check my Eclipse project file into Git,
> I'll need to painfully create a new Eclipse project every time I do a
> clean checkout of the code.
> But the obvious solution of storing my Eclipse project file in Git also
> wouldn't work (I think), because it would have settings that are
> peculiar to me, such as my SSH username.
> I considered having the Java code use Maven for building, because I
> noticed that Eclipse has a Maven project import wizard. So I thought
> that wizard might be a way to pretty painlessly reconstruct (most of?)
> my Eclipse project file each time I wanted a clean checkout of the code
> from git. The downside to this is that even if it works, I'd rather not
> introduce the complexity of Maven at this point if I don't need to.
> It's possible that because of my newness to Eclipse I'm misconceiving
> the problem, but any suggestions are welcome.
Eclipse project files (.project and .classpath) are designed to be
shared and should be checked into git. They don't have your SSH
username in them. The files are just XML text files, so you can browse
them to confirm.
If you use linked folders/resources, you will want to make sure that
they are created using resource or classpath variables. This will allow
other people to easily work with your projects.
Powered by FUDForum
. Page generated in 0.03523 seconds