ETA for release of gjit 0.4?

Dear colleagues,

I am using jgit in my maven project. Since current version is a SNAPSHOT (0.4-SNAPSHOT) I cannot release my project with a SNAPSHOT dependency (maven does not allow it). WHat is the time line for releasing version 0.4 of jgit so I can plan accordingly. Thanks for any info.

Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

fredag 05 december 2008 15:34:36 skrev Farrukh Najmi:

What? Plan? :)

You could name the version something else like 0.3.1.42b27c

It was a long time since we labeled anything. Shawn, how about merging my recent close-file-patches, reverting 3ffa47d9294086fbd1cdeb9b1564f922a23e3c6f and e7307f14c531d52cf231c39d844841c4adaf5e5a and then just call i 0.4 ?

-- robin

# from my pu branch, the latest Tentative build in the update site. Works quite well for
me. Refactoring and 
$ git log --pretty=oneline origin/master..pu
2aafc054446f9b3aecdc01687a6949e4c54be6eb Revert "Rewrite GitMoveDeleteHook to use DirCacheBuilder"
439277860e1e315b7f0cd339b2435cc8311956c1 Revert "Teach GitMoveDeleteHook how to move a folder recursively"
abc44bc6efa47c4c6e3c23f85fe9de9cd8460224 Improve closing of files in error situations.
22e2808ac2915446ed81115b663c684341ce6bdd Close a forgotten reference to the HEAD ref.

OK. I'm not a big fan of reverting code, but I see more value in doing it and getting a "more stable" 0.4 out. So I'll do these reverts and make the 0.4 tag this morning.

Shawn.

Err, uhm. I don't have access to my signing key from work. I'll sign it tonight.

Shawn.

:-)

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.

Maven offers many benefits to projects as described in links below. It takes a little getting used to for project dev team but its not bad. It does not impact consumers of projects negatively in any way.

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 a great project.

Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

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

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.

Shawn.

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.

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

Hi Shawn,

I was wondering if there are any updates on my question on whether we can have a 0.4 release of jgit (no SNAPSHOT). I am ready to release my software but maven wont let me release it because its dependency jgit is a SNAPSHOT release.

As I recall you had planned to release 0.4 and make it available on the maven repo at:

<http://egit.googlecode.com/svn/maven/snapshot-repository/org/spearce/jgit>

I do not see it there yet. Any chance of getting that today? Thanks.

Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

måndag 15 december 2008 23:52:43 skrev Farrukh Najmi:

I cannot deploy it seems (I get a 401 or dav not supported), but since we have a tagged v0.4.0 commit you have a handle to make your own local deployment. It is at least defined what commit the v0.4.0 is. You'll need to modify the pom.xml to make it name the jars properly,

index c370783..467e620 100644
@@ -39,7 +39,7 @@ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     <groupId>org.spearce</groupId>
     <artifactId>jgit</artifactId>
     <packaging>jar</packaging>
-    <version>0.4-SNAPSHOT</version>
+    <version>0.4.0</version>
     <name>jgit</name>
     <url>http://repo.or.cz/w/egit.git</url>
     <mailingLists>

-- robin

Jonas, could you help us on this:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: http://egit.googlecode.com/svn/maven/snapshot-repository//org/spearce/jgit/0.4.0/jgit-0.4.0.jar. Return code is: 401

I added this (nah, naming it release-repository didn't work either)

<repository>
<id>jgit-maven-release-repository</id>
<name>JGit Maven Release Repository</name> <url>https://egit.googlecode.com/svn/maven/snapshot-repository/</url> <uniqueVersion>true</uniqueVersion>
</repository>

(tried all combinations of dav/not-dav, http/https). Seems I don't have a dav provider, but https should work, right?

and to ~/.m2/settings.xml

<servers>
<server>
<id>jgit-maven-snapshot-repository</id> <username>tried both my project email and gmail email</username> <password>nah, won't show you</password>
</server>
</servers>

-- robin

måndag 15 december 2008 23:52:43 skrev Farrukh Najmi:

tisdag 16 december 2008 05:17:33 skrev Robin Rosenberg:

tried <id>jgit-maven-release-repository</id> too ;/

-- robin

Robin Rosenberg <[email protected]> wrote Tue, Dec 16, 2008:

Sorry for the long delay. I completely overlooked this. In case it is still relevant ...

This will end up mixing snapshots and releases ...

Well, I don't know, but I would expect the "dav:" to be required. I used the Google Maven Repository pom.xml[0] as a template, which should give something like:

<repository>
<id>jgit-maven-repository</id>
<name>JGit Maven Repository</name> <url>dav:https://egit.googlecode.com/svn/maven/repository/</url>
</repository>

[0] http://google-maven-repository.googlecode.com/svn/snapshot-repository/com/google/google/1-SNAPSHOT/google-1-20080826.150842-5.pom

Try:

<servers>
<server>
<id>jgit-maven-repository</id> <username>robin.rosenberg</username>
<password>Password from http://code.google.com/hosting/settings</password>
</server>
</servers>

Hope this helps.

Jonas Fonseca