Re: [egit-dev] How to build [EJ]Git?

[Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>]

Am 06.01.2010 17:24, schrieb Jason van Zyl:
> 
> On 2010-01-06, at 10:42 AM, Gunnar Wagenknecht wrote:
> 
>> Am 06.01.2010 15:23, schrieb Jason van Zyl:
>>> My point is if you want the highest degree of participation at the community level then a Maven build is probably what you want.
>>
>> Frankly, that's totally none-sense.
> 
> Really? All the consumers of JGit are Maven-based? 

I think you mixed up the point. It's not about the consumers of JGit
*today*. I don't care if they are Maven based or not. The point is, this
shouldn't matter and this shouldn't cause a situation where other are
locked out. IMO "highest degree of participation at the community level"
is not the majority that uses technology X. It's actually the consumers
that use X+Y+Z...

> Maven comes installed on most Linux distros and OS X. 

I see and because it doesn't come installed on Windows, all the Windows
users shouldn't be allowed to be part of the JGit contributor community?

> You think asking people to install PDE Build or Buckminster to build JGit is practical?

Speaking of pragmatism, I think that I don't want to install *anything*
to be able to checkout, run, create a patch & debug JGit.

But while we are at that point. PDE Build comes with PDE and Eclipse
Plug-in developers will have it. They will also have Ant. AFAIK other
IDEs also have a good Ant story. However, here is another example I
consider pragmatism. I started contributing to Eclipse in 2001. Since
that time I have never had to install PDE Build nor Buckminster nor
Maven nor XYZ to create and submit a patch for any Eclipse project of my
choice. Checkout - open source code in editor - modify - debug. No
single CLI or other piece of software involved. I don't even need to
click a "build" button. That's pragmatism.

I'm fine with running Maven or PDE Build or Buckminster whenever I want
to produce a 'real' build, i.e. something that I'm going to offer for
people to consume. But running tools and scripts for building during
daily development and debugging? No, I don't consider this practical.

> Tycho leverages all the Eclipse technologies like P2, JDT and the
> OSGi goodies. We made real attempts to bridge the gaps. 

That's great to hear. I'm sorry but from the feedback in this thread it
seems to me that the gap is far from being bridged. Obviously PDE needs
some love (i.e. patches *sight*) to deal with other dependency sources
in order to properly setup the build path for JGit. Thus, again -
speaking of pragmatism - something that works for a lot other Eclipse
projects (some of them do also work outside OSGi environments) was
traded against something that is still in development. Hmmm. As much as
I appreciate early adopters ... sometimes this is just not practical.
Usually SCMs have branches for this *sight*.

Anyway, PDE can also be used for *non* OSGi but *plain* Java projects.
It's a great way of managing your dependencies at a granularity that
POMs don't provide. No need to install anything for that. Just download
and unzip an Eclipse Classic SDK and you're ready to import the project
I consider this also very practical. BTW, this should be the same story
for other IDEs as well.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/