Re: [egit-dev] jgit and eclipse meta-data.

["Shawn O. Pearce" <spearce@xxxxxxxxxxx>]

Thomas Hallgren <thomas@xxxxxxx> wrote:
> So in essence, any user that wants to bring jgit into their workspace  
> and just compile it using a normal workspace build it will henceforth be  
> forced to also install m2eclipse?

If you want me to check in .project and .classpath files, yes.

Maybe I'm just really annoyed from adding a pile of dependencies just
to run Jetty inside of JUnit tests, but maintaining two different
classpaths and acquiring all of the resources needed to run the
test suite is a huge pain.  Maven at least automates all of that.

Jetty... I couldn't even find their P2 update site to install their
plugins into my Eclipse workspace.  But their in Maven central and
Maven knows how to use it out of the box.


> On 2010-01-08 16:08, Shawn O. Pearce wrote:
>> Thomas Hallgren<thomas@xxxxxxx>  wrote:
>>    
>>> What was the conclusion regarding jgit? Are you going to check in the
>>> .project, .classpath, and manifest? I think many projects would
>>> appreciate that since it makes it painless to include the project as
>>> part of your workspace build.
>>>      
>> My understanding of that thread was, people want me to check in a
>> copy of the .project and .classpath files which use the m2eclipse
>> classpath container and project nature.

-- 
Shawn.