Re: [JGIT] Request for help
- From
Jonas Fonseca <jonas.fonseca@gmail.com>
- Date
- Sep 3, 2009, 15:38 UTC
- Message-ID
- <2c6b72b30909030838q10b88705gb8c553f2c2d74379@mail.gmail.com>
- In-Reply-To
- <20090903144227.GH1033@spearce.org>
On Thu, Sep 3, 2009 at 10:42, Shawn O. Pearce<spearce@spearce.org> wrote:
Show 12 quoted lines
> Jonas Fonseca <jonas.fonseca@gmail.com> wrote: >> BTW, what is your opinion of making it a bit easier to import and use >> the Maven configuration by putting a pom.xml in the top-level >> directory? The actual pom.xml file responsible for building the jgit >> library can still live on in jgit-maven/ if that is preferable. >> >> I am also thinking about "mavenizing" the .pgm subproject to make it >> easier to browse and search the code from within NetBeans. > > Actually, now that we have forked out of the egit.git repository, > I want to refactor the layout of the JGit project to be more maven > like, and have a proper top-level pom to build things.
What kind of module structure do you have in mind? Do you want to move some of the modules/subdirectories? Some refactoring of the maven setup for JGit back was done back in April in sonatype's (a maven company) JGit clone. It is not signed-off, but can serve as a reference.
- http://github.com/sonatype/JGit/commit/641ae523c496f381a7673f4acfa0acdff9d3913e
The Maven layout in the sonatype clone simply uses the Eclipse project layout.
pom.xml: JGit :: Parent |- org.spearce.jgit/pom.xml: JGit :: Core |- org.spearce.jgit.pgm/pom.xml: JGit :: Programs `- org.spearce.jgit.test/pom.xml: JGit :: Test
However, having tests in a separate module can be both good/bad. For example, they will not automatically get run when you only build the Core module.
Anyway, I would like to help.
-- Jonas Fonseca