From: Shawn O. Pearce Date: Thu, 03 Sep 2009 14:42:27 GMT Subject: Re: [JGIT] Request for help Message-ID: <20090903144227.GH1033@spearce.org> In-Reply-To: <2c6b72b30909030545y4465b5c8j4b2b5587a07762c0@mail.gmail.com> Jonas Fonseca 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. Unfortunately it seems that nobody can program a proper Maven pom for a multi-project project unless they are one of the authors of Maven itself. I watched the Apache MINA team struggle with it until the Maven guys wanted to use their code, and fixed their build. So, this refactoring is waiting for a Maven guru to contribute an improvement. Unfortunately they are all busy... So, to answer your original question, yes, we should make this better, and patches are welcome. My own Maven-fu is just not up to the task. -- Shawn.