From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
To: git@vger.kernel.org
Subject: Re: Newbie questions regarding jgit
Date: Wed, 12 Nov 2008 07:51:21 -0500 [thread overview]
Message-ID: <491AD149.8040905@wellfleetsoftware.com> (raw)
In-Reply-To: <2c6b72b30811111401i3c995889n54407243a1072599@mail.gmail.com>
The jgit team, rocks! You guys are simply awesome in your
responsiveness. Thanks for a great project.
Please let me know if I can help with any maven related issues. Here is
a couple of
links I use to evangelize use of maven in OS projects:
Why Maven Rocks:
<http://farrukhnajmi.blogspot.com/2008/02/why-maven-rocks-in-beginning-there-was.html>
Why Maven - Wiki Page:
<http://ebxmlrr.wiki.sourceforge.net/whymaven>
Here are the main resources I use as reference for maven:
Maven Official Docs:
<http://maven.apache.org/guides/index.html>
Better Builds With Maven:
<http://www.topazproject.org/trac/attachment/wiki/MavenInfo/BetterBuildsWithMaven.pdf?format=raw>
I think it is great that the project supports maven at least partially
today.
I would suggest the project consider maven for all its
build/configuration management at some point in future.
It takes a little learning curve initially (most for dev team members
not users) but pays off handsomely very quickly.
Jonas Fonseca wrote:
...
> On Tue, Nov 11, 2008 at 22:44, Shawn O. Pearce <spearce@spearce.org> wrote:
>
>> Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
>>
>>> I would also like to have a public available maven repository for
>>> JGit. If Shawn or Robin acks, I can look into hosting one in the SVN
>>> area of the Google Code project page. Given the lack of a real release
>>> cycle it probably only makes sense to have a snapshot repository.
>>>
...
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
next prev parent reply other threads:[~2008-11-12 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:44 Newbie questions regarding jgit Farrukh Najmi
2008-11-11 21:12 ` Farrukh Najmi
2008-11-11 21:37 ` Jonas Fonseca
2008-11-11 21:44 ` Shawn O. Pearce
2008-11-11 22:01 ` Jonas Fonseca
2008-11-11 23:11 ` Shawn O. Pearce
2008-11-11 23:48 ` [PATCH] Add maven distribution management info for the new snapshot repository Jonas Fonseca
2008-11-12 0:58 ` Shawn O. Pearce
2008-11-12 1:01 ` Shawn O. Pearce
2008-11-12 2:24 ` Newbie questions regarding jgit Imran M Yousuf
2008-11-12 12:51 ` Farrukh Najmi [this message]
2008-11-12 14:05 ` Farrukh Najmi
2008-11-12 14:33 ` Farrukh Najmi
2008-11-12 17:56 ` Farrukh Najmi
2008-11-12 18:30 ` Jonas Fonseca
2008-11-12 19:29 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2008-11-12 22:36 Robin Rosenberg
2008-11-12 22:37 Robin Rosenberg
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=491AD149.8040905@wellfleetsoftware.com \
--to=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.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).