Menu
▾
▴
javagit-devel — Javagit Developer Issues
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(56) |
Aug
(44) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Multi P. <mul...@gm...> - 2013-08-14 11:19:18
|
Hey guys, I just came across your project implementing a Java library to manage Git repositories. Unfortunately I had to notice you only once released an alpha version 5 years ago! Did you loose interest in continuing the project? Do you want me to refine your Java library? I would take your source code and publish it on GitHub, because I already have a GitHub account. Furthermore in my opinion using SVN in a Git related project looks a bit strange ;). Or do you want to work on it again? Then I ask you for accommodating me after I created an account at sourceforge. best regards, multiprogger |
|
From: <nou...@go...> - 2011-08-21 23:58:59
|
If you have trouble viewing or submitting this form, you can fill it out online: https://docs.google.com/spreadsheet/viewform?formkey=dFo5V2JpdzZYZ3M5N2tweUNYcmxHR3c6MQ Effectiveness of Test Driven Development in Open Source Projects Hello there, My name is Noumi Nooruddeen, currently pursing MSc. Software Engineering in University of Hertfordshire. At present I am on my thesis which is ' The effectiveness of Test Driven Development on code quality'. For this purpose I am observing the open source projects developed on both test driven development and traditional manner. Please take few seconds to fill out this survey, which can eventually help my thesis. Your response will be highly beneficial for me. Thankyou for your time, I really appreciate this. Noumi What is the name of the project that you are working on? * If you are working on more than one OSS project, please fill one survey for each of them Is the project developed using Test Driven Development? * Yes No Powered by Google Docs Report Abuse - Terms of Service - Additional Terms |
|
From: Anirudha J. <ani...@ny...> - 2010-05-08 21:16:59
|
You g9ota see these prices! http://heatsummer.com |
|
From: Vitaly B. <vb...@ve...> - 2008-08-22 18:45:25
|
Sorry Guys sent the wrong patch -----Original Message----- From: Vitaly Babiy <vb...@ve...> To: jav...@li... Subject: [Javagit-devel] Starting with project Date: Fri, 22 Aug 2008 14:31:12 -0400 Hey guys I have started to try to implement the git remote * functionality and I wanted to show you what I have so far so you guys could comment. I have include much javadoc yet but I or unit test but I do plan on doing that when in the future. Thanks, Vitaly Babiy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Javagit-devel mailing list Jav...@li... https://lists.sourceforge.net/lists/listinfo/javagit-devel |
|
From: Vitaly B. <vb...@ve...> - 2008-08-22 18:31:29
|
Hey guys I have started to try to implement the git remote * functionality and I wanted to show you what I have so far so you guys could comment. I have include much javadoc yet but I or unit test but I do plan on doing that when in the future. Thanks, Vitaly Babiy |
|
From: Ross S. <ros...@ny...> - 2008-08-05 09:26:10
|
I rewrote Question #10 in the FAQ (How is JavaGit different from JGit/ EGit?) - anyone have any comments? I committed this, but didn't publish. ===================== JGit is a pure Java implementation of a git client, developed in tandem with EGit, an Eclipse plugin for git. While JGit is mature, full-featured, and flexible, it does have a few drawbacks: 1. Documentation for JGit is sparse. For a developer, using it for a project would mean spending time combing through JGit source; ideally, we wanted an API where a .jar, the JavaDocs, and an introductory HOWTO would be sufficient. 2. It's bound to a pure Java implementation of git functionality. We aimed for an architecture where, if we should later want to hook into native git C (using JNI or some other Java/C bridge), or even provide pure Java implementations, we could do so with no public-facing API impact. 3. JGit is tied on some level to EGit. We'd like to provide a library that's designed to stand on its own from day one. After some consideration, we decided to create our own git API, intended to address the above concerns. We're not trying to take away from JGit - it's far more feature-rich than JavaGit at present. But competition is a good thing, and we hope to bridge that feature gap. |
|
From: Andrew C. <ac...@co...> - 2008-08-04 20:23:42
|
Hey Paul, I was seeing the php errors that you ran into on the website. I think it probably has something to do with a misconfigured sf.net webserver node in which it doesn't look in the current directory path for include files (while the other cluster nodes do). I'm substituting a workaround for both our sites. -- Drew On Mon, 4 Aug 2008, Paul Munson Bethe wrote: > Andrew, > > your changes (648) to GitPull/GitPush have broken the build... > > As we are not exposing those operations in the pre-alpha, I will comment out the calling code in PullPage/PushPage > > Question to all: Why did this not break cruise-control? > > -P > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gitclipse-devel mailing list > Git...@li... > https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > |
|
From: James L. <jam...@gm...> - 2008-08-04 17:41:32
|
Cool. Also: http://freshmeat.net/projects/javagit/?branch_id=75378&release_id=282451 And posted to acm@cs..., fun-at-cims@cims..., gi...@vg...rn... James On Mon, Aug 4, 2008 at 1:08 PM, Ross Snyder <ros...@ny...> wrote: > http://www.reddit.com/comments/6uu4y/ > just_released_javagit_a_new_open_source_java/ > http://digg.com/programming/ > Just_released_JavaGit_open_source_Java_library_for_git > > On Aug 4, 2008, at 12:05 PM, Michael Schidlowsky wrote: > >> Excellent! This is great news! >> >> -Michael >> >> >> On Mon, Aug 4, 2008 at 10:39 AM, James Linder >> <jam...@gm...> wrote: >> Hi All, >> >> The 0.1.0 release files are posted to Sourceforge. The website is >> updated with a news page, a link to the release and the javadocs for >> 0.1.0 alpha. Take a look. >> >> Let's start publicizing the release to the world! :-) >> >> Cheers, >> >> James |
|
From: Anirudha J. <ani...@ny...> - 2008-08-04 17:29:40
|
Mostly likely your user name is not setup in apache(htaccess) access rules. I have updated the content on the site and repo to reflect the changes. Ani On Mon, Aug 4, 2008 at 1:02 PM, Michael Schidlowsky <mic...@cs...>wrote: > I tried to commit some changes to the website this morning and got this > error: > > (12:49:35) exit:128$ svn commit -m "reworded some text in news and cleaned > up left-nav" > Authentication realm: <https://subversive.cims.nyu.edu:443> OSP Repository > Authenticaion > Password for 'mschidlowsky': > svn: Commit failed (details follow): > svn: MKACTIVITY of '/osp/!svn/act/502f4220-a553-0410-8bef-a4093f9e1ba0': > 500 Internal Server Error (https://subversive.cims.nyu.edu) > > Any idea what's causing this? In the meantime, here's my version of > news.html (suggestions welcome): > > > <div> > > <h2>JavaGit News</h2> > > <hr> > > <h3>JavaGit Releases Version 0.1.0 Alpha</h3> > <h4>August 4, 2008</h4> > <p> > The JavaGit team is pleased to announce the release of JavaGit version > 0.1.0 > alpha, a Java API to <a href="http://git.or.cz">Git</a> (the popular > distributed version > control system). The JavaGit API is both friendly to users just getting > the hang of Git and familiar to experts well versed in Git's porcelain > and plumbing. > </p> > <p> > Use JavaGit's <b>command API</b> for access to raw git commands > or the <b>object API</b> for type-safe and Java-friendly access to the > the .git folder, the working tree, and other familiar git concepts. > Visit the <a href="cookbook.php">JavaGit Cookbook</a> to get started. > </p> > <p> > JavaGit is released as open source software under the GNU LGPL license. > </p> > <p> > For additional information on the JavaGit project, please visit: > </p> > </p> > http://www.javagit.com > </p> > > </div> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel > > -- Anirudha P. Jadhav |
|
From: Ross S. <ros...@ny...> - 2008-08-04 17:10:13
|
http://www.reddit.com/comments/6uu4y/ just_released_javagit_a_new_open_source_java/ http://digg.com/programming/ Just_released_JavaGit_open_source_Java_library_for_git On Aug 4, 2008, at 12:05 PM, Michael Schidlowsky wrote: > Excellent! This is great news! > > -Michael > > > On Mon, Aug 4, 2008 at 10:39 AM, James Linder > <jam...@gm...> wrote: > Hi All, > > The 0.1.0 release files are posted to Sourceforge. The website is > updated with a news page, a link to the release and the javadocs for > 0.1.0 alpha. Take a look. > > Let's start publicizing the release to the world! :-) > > Cheers, > > James > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel > > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel |
|
From: Michael S. <mic...@cs...> - 2008-08-04 17:02:24
|
I tried to commit some changes to the website this morning and got this error: (12:49:35) exit:128$ svn commit -m "reworded some text in news and cleaned up left-nav" Authentication realm: <https://subversive.cims.nyu.edu:443> OSP Repository Authenticaion Password for 'mschidlowsky': svn: Commit failed (details follow): svn: MKACTIVITY of '/osp/!svn/act/502f4220-a553-0410-8bef-a4093f9e1ba0': 500 Internal Server Error (https://subversive.cims.nyu.edu) Any idea what's causing this? In the meantime, here's my version of news.html (suggestions welcome): <div> <h2>JavaGit News</h2> <hr> <h3>JavaGit Releases Version 0.1.0 Alpha</h3> <h4>August 4, 2008</h4> <p> The JavaGit team is pleased to announce the release of JavaGit version 0.1.0 alpha, a Java API to <a href="http://git.or.cz">Git</a> (the popular distributed version control system). The JavaGit API is both friendly to users just getting the hang of Git and familiar to experts well versed in Git's porcelain and plumbing. </p> <p> Use JavaGit's <b>command API</b> for access to raw git commands or the <b>object API</b> for type-safe and Java-friendly access to the the .git folder, the working tree, and other familiar git concepts. Visit the <a href="cookbook.php">JavaGit Cookbook</a> to get started. </p> <p> JavaGit is released as open source software under the GNU LGPL license. </p> <p> For additional information on the JavaGit project, please visit: </p> </p> http://www.javagit.com </p> </div> |
|
From: Michael S. <msc...@gm...> - 2008-08-04 16:05:56
|
Excellent! This is great news! -Michael On Mon, Aug 4, 2008 at 10:39 AM, James Linder <jam...@gm...>wrote: > Hi All, > > The 0.1.0 release files are posted to Sourceforge. The website is > updated with a news page, a link to the release and the javadocs for > 0.1.0 alpha. Take a look. > > Let's start publicizing the release to the world! :-) > > Cheers, > > James > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel > > |
|
From: James L. <jam...@gm...> - 2008-08-04 14:40:18
|
Hi All, The 0.1.0 release files are posted to Sourceforge. The website is updated with a news page, a link to the release and the javadocs for 0.1.0 alpha. Take a look. Let's start publicizing the release to the world! :-) Cheers, James |
|
From: James L. <jam...@gm...> - 2008-08-04 04:07:07
|
Hi All, I have tagged version 0.1.0. I will be posting the file to sourceforge in the morning. Cheers, James |
|
From: James L. <jam...@gm...> - 2008-08-03 23:56:33
|
[inline] On Sun, Aug 3, 2008 at 7:19 PM, Ross Snyder <ros...@ny...> wrote: > I'll also write some sample code using the high-level API, and pass it along > later tonight. Cool. Be sure to take a look at what Anirudha is doing too. > I can post to Digg & reddit once we're live. Excellent. Thanks. > Verson 0.1.0 seems right. We're more functional than a 0.0.1, but not as > stable as a 0.5. Yup. > On Aug 3, 2008, at 6:31 PM, James Linder wrote: > >> Hi All, >> >> We are close to ready for cutting the alpha release. Here are the >> final things I see that we need before we can cut the build. Is there >> anything else we should be getting in before cutting the release? >> >> 1. Code samples for the website. Anirhuda is working on them and >> should have some examples ready shortly. >> >> 2. Writing up release notes. I am working on this now. I'll be >> committing them to the repository soon. >> >> 3. Fixes for some final comments about bug 2031803. This is not a >> show stopper, but it would be great to get these changes in before >> releasing. >> >> 4. Writing text for a release notice. I am working on this too. I'll >> post it to the list for feedback shortly. >> >> >> Once we've got these squared away, assuming there are no other >> outstanding changes to make, I'll cut the release. I am writing up >> the process I intend to use and will commit it to the repository in >> the trunk/docs directory. >> >> For posting the release to the world, I figured I would announce it >> via freshmeat.net, ac...@cs..., fun...@li..., >> gi...@vg... and the JavaGit website. Could someone else look >> into posting on programming.reddit, digg, your own blogs, any other >> git-specific sites, JRuby? >> >> >> Finally, I figured we would call it version 0.1.0. Does anyone have >> thoughts or opinions on the version number to start at? >> >> Cheers, >> >> James >> >> On Sun, Aug 3, 2008 at 1:12 AM, James Linder <jam...@gm...> >> wrote: >>> >>> Hi All, >>> >>> Here is the status of the build so far as I see it. Please respond >>> status updates. >>> >>> Still waiting on: >>> >>> - Cookbook-style code samples for the website. Anirhuda, what is the >>> status of the code samples you are working on? >>> >>> - We've fixed some JavaDoc documentation holes. Are there other ones >>> that we should be fixing before release? >>> >>> - Writing text for a release notice to post in publication of our >>> release. >>> >>> - Writing up any release notes. >>> >>> - Figure out how to get JavaGit to show up as a project when searching >>> in Sourceforge for JavaGit >>> >>> - What other bugs are you all fixing that we should get into this >>> build? Please go through the bugs and fix any you can. >>> >>> >>> >>> Done: >>> >>> - Ross's JavaGitConfiguration class and integration. >>> >>> - GitLog has been added. >>> >>> - Moved a good portion of our notes from the OSP class wiki to the >>> JavaGit.com website. >>> >>> - I added the suggested FAQ item from Andrew. For the msysgit/cygwin >>> git problem seen by Paul, I think we can wait and see if other users >>> post about it before putting it up. >>> >>> Cheers, >>> >>> James >>> >>> >>> On Thu, Jul 31, 2008 at 6:51 AM, James Linder <jam...@gm...> >>> wrote: >>>> >>>> Hi All, >>>> >>>> The current plan is to release an Alpha build on Sunday. To hit this >>>> goal, we need to do some prep work. Following is a list of the >>>> highest priority tasks I see us needing to do before the release. If >>>> there are other things you think should be on this highest priority >>>> list, please respond with those items. >>>> >>>> 1. Add some code samples to the website. Create a few pages with >>>> sample code for some basic ways to use the library preferably in a >>>> cookbook style set of pages. A good example to follow is >>>> http://groovy.codehaus.org/Cookbook+Examples . Add the main cookbook >>>> page to the menu under the Documentation section. The code for the >>>> website is now in the repository under "website". >>>> >>>> 2. Fix as many bugs as we can. See what bugs apply to code you have >>>> written and fix them. Please assign the bug to yourself before >>>> starting work on it so others know you are taking responsibility for >>>> it. >>>> >>>> 3. We are waiting on Ross's GitConfig (?) class. >>>> >>>> 4. Add to the FAQ; >>>> - msysgit and cygwin+git conflict information as indicated by Paul. >>>> - The troublueshooting note that Andrew sent to the javagit-users >>>> list on July 21. >>>> - Anything else you can think of that is important. >>>> >>>> 5. Fix any javadoc documentation holes in the api.commands.Git* >>>> classes that we have. Since these will be the primary documentation >>>> points for our users for the near future, it is critical that the >>>> javadocs be thorough and of high-quality. >>>> >>>> 6. Anirudha, add the ...api.commands.GitLog class. >>>> >>>> Cheers, >>>> >>>> James >>>> >>> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Javagit-devel mailing list >> Jav...@li... >> https://lists.sourceforge.net/lists/listinfo/javagit-devel > > |
|
From: Anirudha J. <ani...@ny...> - 2008-08-03 23:43:39
|
Hi Ross, I have just added a few examples using the API on the website could you have a look and review it. http://javagit.sourceforge.net/cookbook.php thanks, Anirudha On Sun, Aug 3, 2008 at 7:19 PM, Ross Snyder <ros...@ny...> wrote: > I'll also write some sample code using the high-level API, and pass > it along later tonight. > > I can post to Digg & reddit once we're live. > > Verson 0.1.0 seems right. We're more functional than a 0.0.1, but > not as stable as a 0.5. > > > On Aug 3, 2008, at 6:31 PM, James Linder wrote: > > > Hi All, > > > > We are close to ready for cutting the alpha release. Here are the > > final things I see that we need before we can cut the build. Is there > > anything else we should be getting in before cutting the release? > > > > 1. Code samples for the website. Anirhuda is working on them and > > should have some examples ready shortly. > > > > 2. Writing up release notes. I am working on this now. I'll be > > committing them to the repository soon. > > > > 3. Fixes for some final comments about bug 2031803. This is not a > > show stopper, but it would be great to get these changes in before > > releasing. > > > > 4. Writing text for a release notice. I am working on this too. I'll > > post it to the list for feedback shortly. > > > > > > Once we've got these squared away, assuming there are no other > > outstanding changes to make, I'll cut the release. I am writing up > > the process I intend to use and will commit it to the repository in > > the trunk/docs directory. > > > > For posting the release to the world, I figured I would announce it > > via freshmeat.net, ac...@cs..., fun...@li..., > > gi...@vg... and the JavaGit website. Could someone else look > > into posting on programming.reddit, digg, your own blogs, any other > > git-specific sites, JRuby? > > > > > > Finally, I figured we would call it version 0.1.0. Does anyone have > > thoughts or opinions on the version number to start at? > > > > Cheers, > > > > James > > > > On Sun, Aug 3, 2008 at 1:12 AM, James Linder > > <jam...@gm...> wrote: > >> Hi All, > >> > >> Here is the status of the build so far as I see it. Please respond > >> status updates. > >> > >> Still waiting on: > >> > >> - Cookbook-style code samples for the website. Anirhuda, what is the > >> status of the code samples you are working on? > >> > >> - We've fixed some JavaDoc documentation holes. Are there other ones > >> that we should be fixing before release? > >> > >> - Writing text for a release notice to post in publication of our > >> release. > >> > >> - Writing up any release notes. > >> > >> - Figure out how to get JavaGit to show up as a project when > >> searching > >> in Sourceforge for JavaGit > >> > >> - What other bugs are you all fixing that we should get into this > >> build? Please go through the bugs and fix any you can. > >> > >> > >> > >> Done: > >> > >> - Ross's JavaGitConfiguration class and integration. > >> > >> - GitLog has been added. > >> > >> - Moved a good portion of our notes from the OSP class wiki to the > >> JavaGit.com website. > >> > >> - I added the suggested FAQ item from Andrew. For the msysgit/cygwin > >> git problem seen by Paul, I think we can wait and see if other users > >> post about it before putting it up. > >> > >> Cheers, > >> > >> James > >> > >> > >> On Thu, Jul 31, 2008 at 6:51 AM, James Linder > >> <jam...@gm...> wrote: > >>> Hi All, > >>> > >>> The current plan is to release an Alpha build on Sunday. To hit > >>> this > >>> goal, we need to do some prep work. Following is a list of the > >>> highest priority tasks I see us needing to do before the > >>> release. If > >>> there are other things you think should be on this highest priority > >>> list, please respond with those items. > >>> > >>> 1. Add some code samples to the website. Create a few pages with > >>> sample code for some basic ways to use the library preferably in a > >>> cookbook style set of pages. A good example to follow is > >>> http://groovy.codehaus.org/Cookbook+Examples . Add the main > >>> cookbook > >>> page to the menu under the Documentation section. The code for the > >>> website is now in the repository under "website". > >>> > >>> 2. Fix as many bugs as we can. See what bugs apply to code you have > >>> written and fix them. Please assign the bug to yourself before > >>> starting work on it so others know you are taking responsibility for > >>> it. > >>> > >>> 3. We are waiting on Ross's GitConfig (?) class. > >>> > >>> 4. Add to the FAQ; > >>> - msysgit and cygwin+git conflict information as indicated by Paul. > >>> - The troublueshooting note that Andrew sent to the javagit-users > >>> list on July 21. > >>> - Anything else you can think of that is important. > >>> > >>> 5. Fix any javadoc documentation holes in the api.commands.Git* > >>> classes that we have. Since these will be the primary documentation > >>> points for our users for the near future, it is critical that the > >>> javadocs be thorough and of high-quality. > >>> > >>> 6. Anirudha, add the ...api.commands.GitLog class. > >>> > >>> Cheers, > >>> > >>> James > >>> > >> > > > > ---------------------------------------------------------------------- > > --- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win > > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in > > the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Javagit-devel mailing list > > Jav...@li... > > https://lists.sourceforge.net/lists/listinfo/javagit-devel > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel > -- Anirudha P. Jadhav |
|
From: James L. <jam...@gm...> - 2008-08-03 23:34:05
|
Hi All, I've written up the following text for our publication notice. Please provide feedback/changes/additions. Thanks, James -------------------------------------------------- JavaGit Releases Version 0.1.0 The JavaGit team is pleased to announce the release of JavaGit version 0.1.0, an API providing access to git repositories from Java programs. The goal of JavaGit is to bring the power of git to the Java developer as an API that is intuitive for developers new to git and developers who are veteran git users. JavaGit is engineered to provide the developer with access to the raw git commands through a command API as well as an object API designed to represent the .git repository, the working tree and other, familiar git concepts. JavaGit uses the git binaries installed on the host machine to proide git functionality and has been designed to easily accommodate additional methods of access to git repositories. JavaGit is released as open source software under the GNU LGPL license. For additional information on the JavaGit project, please visit: http://www.javagit.com |
|
From: Ross S. <ros...@ny...> - 2008-08-03 23:20:45
|
I'll also write some sample code using the high-level API, and pass it along later tonight. I can post to Digg & reddit once we're live. Verson 0.1.0 seems right. We're more functional than a 0.0.1, but not as stable as a 0.5. On Aug 3, 2008, at 6:31 PM, James Linder wrote: > Hi All, > > We are close to ready for cutting the alpha release. Here are the > final things I see that we need before we can cut the build. Is there > anything else we should be getting in before cutting the release? > > 1. Code samples for the website. Anirhuda is working on them and > should have some examples ready shortly. > > 2. Writing up release notes. I am working on this now. I'll be > committing them to the repository soon. > > 3. Fixes for some final comments about bug 2031803. This is not a > show stopper, but it would be great to get these changes in before > releasing. > > 4. Writing text for a release notice. I am working on this too. I'll > post it to the list for feedback shortly. > > > Once we've got these squared away, assuming there are no other > outstanding changes to make, I'll cut the release. I am writing up > the process I intend to use and will commit it to the repository in > the trunk/docs directory. > > For posting the release to the world, I figured I would announce it > via freshmeat.net, ac...@cs..., fun...@li..., > gi...@vg... and the JavaGit website. Could someone else look > into posting on programming.reddit, digg, your own blogs, any other > git-specific sites, JRuby? > > > Finally, I figured we would call it version 0.1.0. Does anyone have > thoughts or opinions on the version number to start at? > > Cheers, > > James > > On Sun, Aug 3, 2008 at 1:12 AM, James Linder > <jam...@gm...> wrote: >> Hi All, >> >> Here is the status of the build so far as I see it. Please respond >> status updates. >> >> Still waiting on: >> >> - Cookbook-style code samples for the website. Anirhuda, what is the >> status of the code samples you are working on? >> >> - We've fixed some JavaDoc documentation holes. Are there other ones >> that we should be fixing before release? >> >> - Writing text for a release notice to post in publication of our >> release. >> >> - Writing up any release notes. >> >> - Figure out how to get JavaGit to show up as a project when >> searching >> in Sourceforge for JavaGit >> >> - What other bugs are you all fixing that we should get into this >> build? Please go through the bugs and fix any you can. >> >> >> >> Done: >> >> - Ross's JavaGitConfiguration class and integration. >> >> - GitLog has been added. >> >> - Moved a good portion of our notes from the OSP class wiki to the >> JavaGit.com website. >> >> - I added the suggested FAQ item from Andrew. For the msysgit/cygwin >> git problem seen by Paul, I think we can wait and see if other users >> post about it before putting it up. >> >> Cheers, >> >> James >> >> >> On Thu, Jul 31, 2008 at 6:51 AM, James Linder >> <jam...@gm...> wrote: >>> Hi All, >>> >>> The current plan is to release an Alpha build on Sunday. To hit >>> this >>> goal, we need to do some prep work. Following is a list of the >>> highest priority tasks I see us needing to do before the >>> release. If >>> there are other things you think should be on this highest priority >>> list, please respond with those items. >>> >>> 1. Add some code samples to the website. Create a few pages with >>> sample code for some basic ways to use the library preferably in a >>> cookbook style set of pages. A good example to follow is >>> http://groovy.codehaus.org/Cookbook+Examples . Add the main >>> cookbook >>> page to the menu under the Documentation section. The code for the >>> website is now in the repository under "website". >>> >>> 2. Fix as many bugs as we can. See what bugs apply to code you have >>> written and fix them. Please assign the bug to yourself before >>> starting work on it so others know you are taking responsibility for >>> it. >>> >>> 3. We are waiting on Ross's GitConfig (?) class. >>> >>> 4. Add to the FAQ; >>> - msysgit and cygwin+git conflict information as indicated by Paul. >>> - The troublueshooting note that Andrew sent to the javagit-users >>> list on July 21. >>> - Anything else you can think of that is important. >>> >>> 5. Fix any javadoc documentation holes in the api.commands.Git* >>> classes that we have. Since these will be the primary documentation >>> points for our users for the near future, it is critical that the >>> javadocs be thorough and of high-quality. >>> >>> 6. Anirudha, add the ...api.commands.GitLog class. >>> >>> Cheers, >>> >>> James >>> >> > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Javagit-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javagit-devel |
|
From: James L. <jam...@gm...> - 2008-08-03 22:31:21
|
Hi All, We are close to ready for cutting the alpha release. Here are the final things I see that we need before we can cut the build. Is there anything else we should be getting in before cutting the release? 1. Code samples for the website. Anirhuda is working on them and should have some examples ready shortly. 2. Writing up release notes. I am working on this now. I'll be committing them to the repository soon. 3. Fixes for some final comments about bug 2031803. This is not a show stopper, but it would be great to get these changes in before releasing. 4. Writing text for a release notice. I am working on this too. I'll post it to the list for feedback shortly. Once we've got these squared away, assuming there are no other outstanding changes to make, I'll cut the release. I am writing up the process I intend to use and will commit it to the repository in the trunk/docs directory. For posting the release to the world, I figured I would announce it via freshmeat.net, ac...@cs..., fun...@li..., gi...@vg... and the JavaGit website. Could someone else look into posting on programming.reddit, digg, your own blogs, any other git-specific sites, JRuby? Finally, I figured we would call it version 0.1.0. Does anyone have thoughts or opinions on the version number to start at? Cheers, James On Sun, Aug 3, 2008 at 1:12 AM, James Linder <jam...@gm...> wrote: > Hi All, > > Here is the status of the build so far as I see it. Please respond > status updates. > > Still waiting on: > > - Cookbook-style code samples for the website. Anirhuda, what is the > status of the code samples you are working on? > > - We've fixed some JavaDoc documentation holes. Are there other ones > that we should be fixing before release? > > - Writing text for a release notice to post in publication of our release. > > - Writing up any release notes. > > - Figure out how to get JavaGit to show up as a project when searching > in Sourceforge for JavaGit > > - What other bugs are you all fixing that we should get into this > build? Please go through the bugs and fix any you can. > > > > Done: > > - Ross's JavaGitConfiguration class and integration. > > - GitLog has been added. > > - Moved a good portion of our notes from the OSP class wiki to the > JavaGit.com website. > > - I added the suggested FAQ item from Andrew. For the msysgit/cygwin > git problem seen by Paul, I think we can wait and see if other users > post about it before putting it up. > > Cheers, > > James > > > On Thu, Jul 31, 2008 at 6:51 AM, James Linder <jam...@gm...> wrote: >> Hi All, >> >> The current plan is to release an Alpha build on Sunday. To hit this >> goal, we need to do some prep work. Following is a list of the >> highest priority tasks I see us needing to do before the release. If >> there are other things you think should be on this highest priority >> list, please respond with those items. >> >> 1. Add some code samples to the website. Create a few pages with >> sample code for some basic ways to use the library preferably in a >> cookbook style set of pages. A good example to follow is >> http://groovy.codehaus.org/Cookbook+Examples . Add the main cookbook >> page to the menu under the Documentation section. The code for the >> website is now in the repository under "website". >> >> 2. Fix as many bugs as we can. See what bugs apply to code you have >> written and fix them. Please assign the bug to yourself before >> starting work on it so others know you are taking responsibility for >> it. >> >> 3. We are waiting on Ross's GitConfig (?) class. >> >> 4. Add to the FAQ; >> - msysgit and cygwin+git conflict information as indicated by Paul. >> - The troublueshooting note that Andrew sent to the javagit-users >> list on July 21. >> - Anything else you can think of that is important. >> >> 5. Fix any javadoc documentation holes in the api.commands.Git* >> classes that we have. Since these will be the primary documentation >> points for our users for the near future, it is critical that the >> javadocs be thorough and of high-quality. >> >> 6. Anirudha, add the ...api.commands.GitLog class. >> >> Cheers, >> >> James >> > |
|
From: James L. <jh...@ny...> - 2008-08-03 18:43:09
|
Hi All, Since we are writing an API and the API documentation is of great importance, I looked around for some information on how Sun does documentation for Java itself and for more detailed information on how to use JavaDocs. The following links are quite good. javadoc - The Java API Documentation Generator http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/javadoc.html How to Write Doc Comments for the Javadoc Tool http://java.sun.com/j2se/javadoc/writingdoccomments/index.html Requirements for Writing Java API Specifications http://java.sun.com/j2se/javadoc/writingapispecs/index.html Cheers, James |
|
From: Gurdeep D. <gs...@ny...> - 2008-08-03 16:47:36
|
Ref: Bug [ 2036823 ] Change *Iterator to *Iterable methods in GitStatusResponse Hi I have renamed the methods in GitStatusResponse and removed the word iterator completely from method names. You will need to make changes to your gitclipse code accordingly. e.g. the method that was earlier getNewFilesToCommitIteator() is now just getFilesToCommit() thanks Gurdeep New method signatures -------------------------------- public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() |
|
From: James L. <jam...@gm...> - 2008-08-03 14:53:52
|
Hi Anirudha, Excellent. :-) In the mean time, could you upload some of what you have to the website so we can see what you already have and perhaps provide some feedback? Thanks, James On Sun, Aug 3, 2008 at 6:22 AM, <ani...@ny...> wrote: > hello, > > I have been working on the examples, most of the examples are bases on > the official git tutorial and recipies. I will checkin my final > version around 4 today. > > Thanks > On 8/3/08, James Linder <jam...@gm...> wrote: >> Hi All, >> >> Here is the status of the build so far as I see it. Please respond >> status updates. >> >> Still waiting on: >> >> - Cookbook-style code samples for the website. Anirhuda, what is the >> status of the code samples you are working on? >> >> - We've fixed some JavaDoc documentation holes. Are there other ones >> that we should be fixing before release? >> >> - Writing text for a release notice to post in publication of our release. >> >> - Writing up any release notes. >> >> - Figure out how to get JavaGit to show up as a project when searching >> in Sourceforge for JavaGit >> >> - What other bugs are you all fixing that we should get into this >> build? Please go through the bugs and fix any you can. >> >> >> >> Done: >> >> - Ross's JavaGitConfiguration class and integration. >> >> - GitLog has been added. >> >> - Moved a good portion of our notes from the OSP class wiki to the >> JavaGit.com website. >> >> - I added the suggested FAQ item from Andrew. For the msysgit/cygwin >> git problem seen by Paul, I think we can wait and see if other users >> post about it before putting it up. >> >> Cheers, >> >> James >> >> >> On Thu, Jul 31, 2008 at 6:51 AM, James Linder <jam...@gm...> >> wrote: >>> Hi All, >>> >>> The current plan is to release an Alpha build on Sunday. To hit this >>> goal, we need to do some prep work. Following is a list of the >>> highest priority tasks I see us needing to do before the release. If >>> there are other things you think should be on this highest priority >>> list, please respond with those items. >>> >>> 1. Add some code samples to the website. Create a few pages with >>> sample code for some basic ways to use the library preferably in a >>> cookbook style set of pages. A good example to follow is >>> http://groovy.codehaus.org/Cookbook+Examples . Add the main cookbook >>> page to the menu under the Documentation section. The code for the >>> website is now in the repository under "website". >>> >>> 2. Fix as many bugs as we can. See what bugs apply to code you have >>> written and fix them. Please assign the bug to yourself before >>> starting work on it so others know you are taking responsibility for >>> it. >>> >>> 3. We are waiting on Ross's GitConfig (?) class. >>> >>> 4. Add to the FAQ; >>> - msysgit and cygwin+git conflict information as indicated by Paul. >>> - The troublueshooting note that Andrew sent to the javagit-users >>> list on July 21. >>> - Anything else you can think of that is important. >>> >>> 5. Fix any javadoc documentation holes in the api.commands.Git* >>> classes that we have. Since these will be the primary documentation >>> points for our users for the near future, it is critical that the >>> javadocs be thorough and of high-quality. >>> >>> 6. Anirudha, add the ...api.commands.GitLog class. >>> >>> Cheers, >>> >>> James >>> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Javagit-devel mailing list >> Jav...@li... >> https://lists.sourceforge.net/lists/listinfo/javagit-devel >> > > > -- > Anirudha P. Jadhav > |
|
From: Gurdeep D. <gs...@ny...> - 2008-08-03 08:08:16
|
Hi Andrew, I need some more information regarding this bug and your reply to my following questions will help me troubleshoot the issue quicker. thanks Gurdeep -------------------------------------------- When I have a project in: /home/acase/projects/runtime-EclipseApplication/hello > What is the root of the repository. Is /home/acase/projects/runtime- EclipseApplication/hello directory the root of the repository. With untracked files: .classpath .project bin It passes back the iterator with files: untracked: /home/acase/.classpath untracked: /home/acase/.project untracked: /home/acase/bin > Do these files (I mean another set of same name files) under your home directory really exist. These aren't valid files. It should be: /home/acase/projects/runtime-EclipseApplication/hello/.classpath /home/acase/projects/runtime-EclipseApplication/hello/.project /home/acase/projects/runtime-EclipseApplication/hello/bin > Can you send me the output of the git-status command run manually on the command-line from the root of the repository. |
|
From: James L. <jam...@gm...> - 2008-08-03 05:12:56
|
Hi All, Here is the status of the build so far as I see it. Please respond status updates. Still waiting on: - Cookbook-style code samples for the website. Anirhuda, what is the status of the code samples you are working on? - We've fixed some JavaDoc documentation holes. Are there other ones that we should be fixing before release? - Writing text for a release notice to post in publication of our release. - Writing up any release notes. - Figure out how to get JavaGit to show up as a project when searching in Sourceforge for JavaGit - What other bugs are you all fixing that we should get into this build? Please go through the bugs and fix any you can. Done: - Ross's JavaGitConfiguration class and integration. - GitLog has been added. - Moved a good portion of our notes from the OSP class wiki to the JavaGit.com website. - I added the suggested FAQ item from Andrew. For the msysgit/cygwin git problem seen by Paul, I think we can wait and see if other users post about it before putting it up. Cheers, James On Thu, Jul 31, 2008 at 6:51 AM, James Linder <jam...@gm...> wrote: > Hi All, > > The current plan is to release an Alpha build on Sunday. To hit this > goal, we need to do some prep work. Following is a list of the > highest priority tasks I see us needing to do before the release. If > there are other things you think should be on this highest priority > list, please respond with those items. > > 1. Add some code samples to the website. Create a few pages with > sample code for some basic ways to use the library preferably in a > cookbook style set of pages. A good example to follow is > http://groovy.codehaus.org/Cookbook+Examples . Add the main cookbook > page to the menu under the Documentation section. The code for the > website is now in the repository under "website". > > 2. Fix as many bugs as we can. See what bugs apply to code you have > written and fix them. Please assign the bug to yourself before > starting work on it so others know you are taking responsibility for > it. > > 3. We are waiting on Ross's GitConfig (?) class. > > 4. Add to the FAQ; > - msysgit and cygwin+git conflict information as indicated by Paul. > - The troublueshooting note that Andrew sent to the javagit-users > list on July 21. > - Anything else you can think of that is important. > > 5. Fix any javadoc documentation holes in the api.commands.Git* > classes that we have. Since these will be the primary documentation > points for our users for the near future, it is critical that the > javadocs be thorough and of high-quality. > > 6. Anirudha, add the ...api.commands.GitLog class. > > Cheers, > > James > |
|
From: James L. <jam...@gm...> - 2008-08-02 20:49:23
|
Excellent. :-) Thanks, James On Sat, Aug 2, 2008 at 4:34 PM, Nutan Singh <ns...@ci...> wrote: > Done. > > -Nutan > > On Sat, Aug 2, 2008 at 4:13 PM, James Linder <jam...@gm...> > wrote: >> >> Hi Nutan, >> >> Thanks for asking about thees bugs. >> >> I've closed and marked as part of the "v0.1.0 (fixed in)" group the >> first one with a note because it's been fixed for 10 days already. If >> it continues to be broken after the release, a new bug should be >> opened for it. >> >> For the second bug, I see the JavaDocs for GitMv have been updated >> with information about what the response object should contain. Could >> you also add the following sentence to the class-level JavaDoc for >> GitMvResponse: >> >> For information about the contents of GitMvResponse instances >> returned by a given method, please see the JavaDoc for the >> method in question. >> >> Once this sentence is added, close the bug. >> >> I also closed and marked as part of the "v0.1.0 (fixed in)" group the >> third bug. >> >> Cheers, >> >> James >> >> >> On Sat, Aug 2, 2008 at 1:41 PM, Nutan Singh <ns...@ci...> wrote: >> > There are 3 bugs fixed but still opened (for a few days). The person who >> > reported them should have a look and accept or reject the fix. Those >> > are: >> > >> > >> > https://sourceforge.net/tracker/index.php?func=detail&aid=2026816&group_id=233450&atid=1089899 >> > >> > https://sourceforge.net/tracker/index.php?func=detail&aid=2033200&group_id=233450&atid=1089899 >> > >> > https://sourceforge.net/tracker/index.php?func=detail&aid=2033420&group_id=233450&atid=1089899 >> > >> > ~Nutan >> > >> > On Sat, Aug 2, 2008 at 1:25 PM, James Linder <jam...@gm...> >> > wrote: >> >> >> >> I like a bug reporting and resolution process similar to the following: >> >> >> >> 1. Someone reports a bug. >> >> 2. Bug gets assigned to someone or picked up by developer. >> >> 3. Developer fixes bug and commits code. >> >> 4. Developer modifies bug with any information that is relevant to the >> >> bug. >> >> 5. Developer changes the "Resolution" to "Fixed" >> >> 6. Reporter should verify the bug is fixed and mark the "Resolution" >> >> as "Accepted" and closes the bug. >> >> 6a. Sometimes/often the reporter will not be the correct person for >> >> closing the bug. In such cases, an appropriate person would make the >> >> change. >> >> >> >> Cheers, >> >> >> >> James >> >> >> >> >> >> On Sat, Aug 2, 2008 at 1:19 PM, Gurdeep Dhindsa <gs...@ny...> wrote: >> >> > >> >> > What is the procedure we are following after fixing the bugs? >> >> > >> >> > Do we close the bug after fixing it or the person who opened the bug >> >> > report will close it ? >> >> > >> >> > thanks >> >> > Gurdeep >> >> > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------- >> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> >> > challenge >> >> > Build the coolest Linux based applications with Moblin SDK & win >> >> > great >> >> > prizes >> >> > Grand prize is a trip for two to an Open Source event anywhere in the >> >> > world >> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> >> > _______________________________________________ >> >> > Javagit-devel mailing list >> >> > Jav...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/javagit-devel >> >> > >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> >> challenge >> >> Build the coolest Linux based applications with Moblin SDK & win great >> >> prizes >> >> Grand prize is a trip for two to an Open Source event anywhere in the >> >> world >> >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> >> _______________________________________________ >> >> Javagit-devel mailing list >> >> Jav...@li... >> >> https://lists.sourceforge.net/lists/listinfo/javagit-devel >> >> >> > >> > >> > > |
