git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [JGIT] Request for help

From
Gabe <gabriel.mcarthur@gmail.com>
Date
Sep 4, 2009, 23:47 UTC
Message-ID
<524457d10909041647u562601d5q69142eefe894ac5b@mail.gmail.com>
In-Reply-To
<658028.86274.qm@web27804.mail.ukl.yahoo.com>
On Fri, Sep 4, 2009 at 10:28 AM, Mark Struberg<struberg@yahoo.de> wrote:
Show 9 quoted lines
> Hi!
>
> Work has been done at
>
> http://github.com/sonatype/JGit/tree/mavenize
>
> Please feel free to pull/fork and share your changes! I'd be happy to pull it in.
>
> @Gabe: your patch seems to got filtered by the list, I think sharing such big things is easier by using github. Would be cool if you could help us!

Ok, I'll fork and send a patch request shortly. I was thinking about it earlier, and I may add a couple of features that all OS projects should follow (e.g. License in the jar, etc.).

As to a few questions that have been raised:
1) I pick the 'sources' folder because it's good metadata management.
Everything in the root folder should be about or related to managing
the project.  No direct source folders, as it clutters the layout.
Best to be perfectly clear where all the action is happening.  It's a
simple convention I wished more projects followed.
2) I haven't worked with the find-bugs plugin.  I looked it up, but it
seems to only generate documents in the 'site'/reporting profile.
Thus it wouldn't necessarily affect the building of the software.  It
would really only be useful if you had something like a Hudson CI
infrastructure or site generation going on to build a website and show
the reports.  I could certainly add that, though, if you like.
3) The LICENSE file can be at the top level.  Not really an issue for
me one way or another.  Just a personal preference on how I have
structured all of my previous Maven projects.
-Gabe
Show 68 quoted lines
>
> LieGrue,
> strub
>
> --- On Fri, 9/4/09, Mark Struberg <struberg@yahoo.de> wrote:
>
>> From: Mark Struberg <struberg@yahoo.de>
>> Subject: Re: [JGIT] Request for help
>> To: "Douglas Campos" <douglas@theros.info>
>> Cc: "Jonas Fonseca" <jonas.fonseca@gmail.com>, git@vger.kernel.org, "Gabe McArthur" <gabriel.mcarthur@gmail.com>
>> Date: Friday, September 4, 2009, 4:49 PM
>> Hi Douglas!
>>
>> http://github.com/sonatype/JGit
>>
>> The branch will be called mavenizing or so.
>>
>> Will post this after I got the tests running.
>>
>> LieGrue,
>> strub
>>
>> --- On Fri, 9/4/09, Douglas Campos <douglas@theros.info>
>> wrote:
>>
>> > From: Douglas Campos <douglas@theros.info>
>> > Subject: Re: [JGIT] Request for help
>> > To: "Mark Struberg" <struberg@yahoo.de>
>> > Cc: "Jonas Fonseca" <jonas.fonseca@gmail.com>,
>> git@vger.kernel.org,
>> "Gabe McArthur" <gabriel.mcarthur@gmail.com>
>> > Date: Friday, September 4, 2009, 4:44 PM
>> > On Fri, Sep 4, 2009
>> > at 9:47 AM, Mark Struberg <struberg@yahoo.de>
>> > wrote:
>> >
>> >
>> > as an old saying tells us: how to climb a mountain?
>> step
>> > after step! ;)
>> >
>> >
>> >
>> > I suggest we create a fresh branch based on the
>> Shawns
>> > current version and add all the features
>> incrementally.
>> >
>> >
>> >
>> > please point out where this branch will happen, I want
>> to
>> > give some help too.
>> >
>> >
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
>
>
Previous: Mark StrubergNext: Douglas Campos
Message 6 of 10 in “Re: [JGIT] Request for help”
  1. Mark StrubergSep 4, 2009
  2. Mark StrubergSep 4, 2009
  3. Jonas FonsecaSep 4, 2009
  4. Mark StrubergSep 4, 2009
  5. Mark StrubergSep 4, 2009
  6. GabeSep 4, 2009
  7. Douglas CamposSep 5, 2009
  8. Gabe McArthurSep 5, 2009
  9. Robin RosenbergSep 5, 2009
  10. Mark StrubergSep 5, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.