Re: ETA for release of gjit 0.4?

From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
Date: Dec 8, 2008, 16:35 UTC
Message-ID: <493D4CDB.2010100@wellfleetsoftware.com>
In-Reply-To: <20081208162123.GD31551@spearce.org>

Shawn O. Pearce wrote:

Show 17 quoted lines

> Farrukh Najmi <farrukh@wellfleetsoftware.com> wrote:
>   
>> I could but maven (and good project release) practices are that a  
>> project's release version should be managed by the project and not  
>> consumers of the project.
>>
>> BTW, If there is interest in maveninzing the project I can offer to  
>> contribute that change to the project. Just let me know if that is  
>> something the project wishes to do.
>>     
>
> Have you seen the jgit-maven subdirectory?  It has a jgit/pom.xml
> contributed by Imran M Yousuf for exactly this reason.  I think we
> also have a Maven distribution site:
>
>   http://code.google.com/p/egit/wiki/ConfiguringMaven
>

That work is commendable but it a workaround to adding maven packaging to a build and release process that is essentially not maven. This provides an important value that maven users such as myself get access to jgit via a maven repo. However, it does not help improve how the project manages its build and release processes.

> The issue is getting one of the developers to tag and upload a build.
> Myself, I don't actually use Maven, so I don't build with it.
>

A completely maven based project would make above really simple and easy to manage using the maven-release-plugin and various other maven facilities. Changing version labels throughout code base, committing modified code, tagging, packaging, uploading etc. would all become automatic with a completely maven based code base. Maven seems like it is too complex and not worth the trouble in first glance (I felt that way at one point). However, a more careful examination reveals that it brings a lot of automated discipline, convenience and simplicity to numerous project tasks. Perhaps Imran and others could chime in on this issue to help make the case for mavenizing the project more completely.

Again, I have made my case for maven previously in the following links:

Background blog: <http://farrukhnajmi.blogspot.com/2008/02/why-maven-rocks-in-beginning-there-was.html>

More useful link: <http://ebxmlrr.wiki.sourceforge.net/whymaven>

Thanks for your consideration of the suggestion.

-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com