From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: ETA for release of gjit 0.4?
Date: Mon, 08 Dec 2008 11:35:39 -0500 [thread overview]
Message-ID: <493D4CDB.2010100@wellfleetsoftware.com> (raw)
In-Reply-To: <20081208162123.GD31551@spearce.org>
Shawn O. Pearce wrote:
> 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
next prev parent reply other threads:[~2008-12-08 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:34 ETA for release of gjit 0.4? Farrukh Najmi
2008-12-06 18:47 ` Robin Rosenberg
2008-12-06 18:57 ` Farrukh Najmi
2008-12-08 16:21 ` Shawn O. Pearce
2008-12-08 16:35 ` Farrukh Najmi [this message]
2008-12-15 22:52 ` Farrukh Najmi
2008-12-16 3:56 ` Robin Rosenberg
2008-12-16 4:17 ` Robin Rosenberg
2008-12-16 4:23 ` Robin Rosenberg
2009-01-14 3:14 ` Jonas Fonseca
2008-12-08 16:52 ` Shawn O. Pearce
2008-12-08 17:13 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493D4CDB.2010100@wellfleetsoftware.com \
--to=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).