You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(30) |
Aug
(79) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
From: SourceForge.net <no...@so...> - 2011-12-09 13:46:49
|
Bugs item #3455431, was opened at 2011-12-09 05:46 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=3455431&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: CLI Implementation Group: New Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: Error parsing commit comment from git log Initial Comment: The git log parser will incorrectly parse an empty message if a commit message begins with a non-numeric token followed by a '-' token. e.g. A commit with the message "JIRA-1234 - Checkpoint: fixed more bugs" will be parsed as "". The reason is evident in the last block of CliGitLog.parseLine() where the parsing of file data begins. It falsely assumes that a legitimate comment message cannot exist as above. Suggest fix: Since it seems that git prints out all the commit messages with a white-space indent it is easy to differentiate a message from file summary data. Add something like: if (line.startsWith(" ")){ response.setMessage(line); return; } to the start of that block or as a prior if-else condition ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=3455431&group_id=233450 |
From: SourceForge.net <no...@so...> - 2011-10-28 00:00:42
|
Bugs item #3429476, was opened at 2011-10-28 00:00 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=3429476&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ron Midthun () Assigned to: Nobody/Anonymous (nobody) Summary: status fails with submodules Initial Comment: I know the project is dead, but in case anyone runs across it... The git status code does not work with projects containing submodules. There's a state variable outputState that is set on the phrases "Changes to be committed", "Changed but not updated", and "Untracked files". This variable has NO default and is otherwise undefined. A git repo with submodules can return the value # On branch ios5_compatibility-1.0 # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: vendor/openfeint (new commits) # Which will fail because addModifiedFile expects outputState to be set. Atlassian Bamboo is using this code, which is where we found the failure. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=3429476&group_id=233450 |
From: SourceForge.net <no...@so...> - 2009-11-18 12:55:58
|
Feature Requests item #2899776, was opened at 2009-11-18 08:55 Message generated for change (Settings changed) made by felipelalli You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2899776&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None >Priority: 3 Private: No Submitted By: br.org.fml (felipelalli) Assigned to: Nobody/Anonymous (nobody) Summary: pure java git implementation Initial Comment: I need it, it's really important to me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2899776&group_id=233450 |
From: SourceForge.net <no...@so...> - 2009-11-18 12:55:26
|
Feature Requests item #2899776, was opened at 2009-11-18 08:55 Message generated for change (Tracker Item Submitted) made by felipelalli You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2899776&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: br.org.fml (felipelalli) Assigned to: Nobody/Anonymous (nobody) Summary: pure java git implementation Initial Comment: I need it, it's really important to me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2899776&group_id=233450 |
From: SourceForge.net <no...@so...> - 2009-06-02 01:43:52
|
Bugs item #2799748, was opened at 2009-06-02 01:43 Message generated for change (Tracker Item Submitted) made by r_g_l_d You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2799748&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rougald (r_g_l_d) Assigned to: Nobody/Anonymous (nobody) Summary: Problem running under Windows Initial Comment: I tried to run JavaGit under Windows XP (Or windows of any kind I guess would do), and came across a problem to even run the simplest cookbook line. The problem originated with JavaGitConfiguration.setGitPath, which calls eventually determineGitVersion, which checks if "git" is in the path specified. The line there "gitPrefix = path.getAbsolutePath() + File.pathSeparator;" is problematic (Also in "getGitCommandPrefix()" since it tries to create the following for Windows: "C:\JavaGitPathSpecified\;git --version" as the command line. Two problems here: 1. We should be able to either add a suffix (Make it git.exe, otherwise the file won't be found?) 2. Give the actual git.exe path, since the above doesn't run. Not sure if it's a problem for Unix (Although it seems to me "C:\JavaGitPathSpecified\:git --version" is equally problematic), but it sure is for Windows. Wouldn't mind sending a patch once verified. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2799748&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-14 14:58:00
|
Bugs item #2051627, was opened at 2008-08-14 10:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2051627&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Misc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul M Bethe (pbethe) Assigned to: Nobody/Anonymous (nobody) Summary: Concurrency problem throws a regular JavaGitException Initial Comment: edu.nyu.cs.javagit.api.JavaGitException: 1. fatal: unable to create '/Users/michelleosborne/dev/code_test/.git/index.lock': File exists at edu.nyu.cs.javagit.client.cli.CliGitStatus.handleErrorState(CliGitStatus.java:156) at The above is a partial stack-trace from a run where we are trying to call git status, while another process is in the middle of doing something else. The error message, makes it clear that there is a concurrency issue. I think perhaps a descendant of JavaGitException like JavaGitConcurrentAccessException would be useful for us. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2051627&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-09 20:21:12
|
Feature Requests item #2031734, was opened at 2008-07-29 14:31 Message generated for change (Comment added) made by ma1683 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2031734&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Paul M Bethe (pbethe) Assigned to: Nobody/Anonymous (nobody) Summary: GitStatusResponse API Initial Comment: None of the methods in the GitStatus Response really do what I want: I have a list/array of files. I want to call GitStatus once, then iterate over my list and get the status of each file. eg. GitStatusResponse gsr = new GitStatus().status(myroot); for (File f : myfileList) { stat.add(gsr.getStatus(f)); } or something like that. Currently that does not seem to be possible in the existing api. ---------------------------------------------------------------------- >Comment By: Maxim A. (ma1683) Date: 2008-08-09 16:21 Message: Logged In: YES user_id=2155661 Originator: NO I have added a new method to GitStatusResponse class: getFileStatus(), which takes java.io.File object as a parameter and return GitFileSystemObject.Status value. For the simplest example, check out getFileStatus() in GitStatus.java (/javagit/trunk/javagit/src/main/java/edu/nyu/cs/javagit/api/commands). That should allow you to query the status of any file the way you wanted. ---------------------------------------------------------------------- Comment By: Maxim A. (ma1683) Date: 2008-08-02 14:06 Message: Logged In: YES user_id=2155661 Originator: NO Paul, I apologize, I actually misunderstood your original question. However, if you use API, you can still get list of GitFileSystemObjects from WorkingTree (getTree()) and then iterate through the list and call getStatus() on each object. There is one complication: you have to check if GitFileSystemObject object is a GitFile object, and then convert it to one, before you call getStatus(). ---------------------------------------------------------------------- Comment By: Maxim A. (ma1683) Date: 2008-08-02 13:52 Message: Logged In: YES user_id=2155661 Originator: NO There is a different way to get the status of the of a file. You can use higher level API. WorkingTree class has a method GitFile getFile(File file), which returns you an instance of GitFile. You can then simply call GitFile's getStatus() method. If you really do not want to use that API, I've also recently added a new method to GitStatus: getFileStatus(). Then you can simply do the following: File repositoryDirectory; /* init repository directory... */ File myFile("foo"); GitFileSystemObject.Status status = new GitStatus().getSingleFileStatus(repositoryDirectory, myFile); GitFileSystemObject.Status is an enumeration. See GitFileSystemObject.java for details. ---------------------------------------------------------------------- Comment By: Paul M Bethe (pbethe) Date: 2008-07-29 19:00 Message: Logged In: YES user_id=308431 Originator: YES ALSO, in this new getStatus method, please consider returning untracked for files which are in an untracked folder. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2031734&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-08 22:41:56
|
Feature Requests item #2035502, was opened at 2008-08-01 21:01 Message generated for change (Settings changed) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2035502&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 5 Private: No Submitted By: James H. Linder (jhlinder) >Assigned to: nutans (nutans) Summary: Git Clone Initial Comment: Implement the GitClone command. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2035502&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-07 02:58:57
|
Bugs item #2037045, was opened at 2008-08-03 15:17 Message generated for change (Comment added) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 4 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Move basic method argument checks from IGit* to Git* Initial Comment: Right now, method argument checks are being done in either the Git* methods, the CLI implementations of the IGit* interfaces, or both. Since the end user should only ever use the classes under edu.nyu.cs.javagit.api, it makes sense to only make the basic argument checks in the ...api.commands.Git* methods and not in the implementations of the ...client.IGit* interfaces. Move all basic argument checks to the edu.nyu.cs.javagit.api.commands.Git* methods. ---------------------------------------------------------------------- >Comment By: nutans (nutans) Date: 2008-08-06 22:58 Message: Logged In: YES user_id=2152864 Originator: NO I have done it for GitMv and GitBranch. ~Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 15:17 Message: Logged In: YES user_id=1099750 Originator: YES This bug can wait until after the 0.1.0 build. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 17:46:13
|
Bugs item #2037398, was opened at 2008-08-04 13:09 Message generated for change (Comment added) made by anirudha81 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Object API Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Anirudha (anirudha81) Assigned to: Nobody/Anonymous (nobody) Summary: GitAdd in WorkingTree.java does not add files Initial Comment: //Create a new directory to be used as a git repository. repositoryDirectory = FileUtilities.createTempDirectory("Demo_gitRepository"); //Initialize the repository ,similar to git init HelperGitCommands.initRepo(repositoryDirectory); //Create a file in our repository File file = FileUtilities.createFile(repositoryDirectory, "README", "First file in the git repository"); //get the instance of the dotGit Object dotGit = DotGit.getInstance(repositoryDirectory); //get the current working tree from the git repository WorkingTree wt = dotGit.getWorkingTree(); GitAddResponse ar = wt.add(); wt.commitAll("First commit to the git repository"); //Commit fails saying no files added ??? wt.gitADD is not adding files, response object is empty. ---------------------------------------------------------------------- >Comment By: Anirudha (anirudha81) Date: 2008-08-05 23:16 Message: Logged In: YES user_id=1014478 Originator: YES see previous comment ---------------------------------------------------------------------- Comment By: Anirudha (anirudha81) Date: 2008-08-05 23:15 Message: Logged In: YES user_id=1014478 Originator: YES Fixed: Modified gitAdd to handle relative paths. and also gitFileSystemObject. reason : GitAdd always assumed files to be relative to the repodir, but using the GitFileSystem Obj. absolute paths were returned to Git Add.Thus always failing the API implementation of git Add. more test cases are needed to correctly test the GIT Object API. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-04 18:25 Message: Logged In: YES user_id=2152864 Originator: NO Hi Anirudha, Shouldn't GitAddResponse ar = wt.add() be GitAddResponse ar = wt.add(file)? Otherwise, I don't see the file getting added to the repository. ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 17:45:43
|
Bugs item #2037398, was opened at 2008-08-04 13:09 Message generated for change (Comment added) made by anirudha81 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Object API Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Anirudha (anirudha81) Assigned to: Nobody/Anonymous (nobody) Summary: GitAdd in WorkingTree.java does not add files Initial Comment: //Create a new directory to be used as a git repository. repositoryDirectory = FileUtilities.createTempDirectory("Demo_gitRepository"); //Initialize the repository ,similar to git init HelperGitCommands.initRepo(repositoryDirectory); //Create a file in our repository File file = FileUtilities.createFile(repositoryDirectory, "README", "First file in the git repository"); //get the instance of the dotGit Object dotGit = DotGit.getInstance(repositoryDirectory); //get the current working tree from the git repository WorkingTree wt = dotGit.getWorkingTree(); GitAddResponse ar = wt.add(); wt.commitAll("First commit to the git repository"); //Commit fails saying no files added ??? wt.gitADD is not adding files, response object is empty. ---------------------------------------------------------------------- >Comment By: Anirudha (anirudha81) Date: 2008-08-05 23:15 Message: Logged In: YES user_id=1014478 Originator: YES Fixed: Modified gitAdd to handle relative paths. and also gitFileSystemObject. reason : GitAdd always assumed files to be relative to the repodir, but using the GitFileSystem Obj. absolute paths were returned to Git Add.Thus always failing the API implementation of git Add. more test cases are needed to correctly test the GIT Object API. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-04 18:25 Message: Logged In: YES user_id=2152864 Originator: NO Hi Anirudha, Shouldn't GitAddResponse ar = wt.add() be GitAddResponse ar = wt.add(file)? Otherwise, I don't see the file getting added to the repository. ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 13:04:35
|
Feature Requests item #2033472, was opened at 2008-07-31 10:06 Message generated for change (Comment added) made by anirudha81 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: v0.2.0 (target) Status: Open Resolution: None Priority: 8 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Anirudha (anirudha81) Summary: Git Init Initial Comment: Git Init is essential for testing gitclipse. ---------------------------------------------------------------------- >Comment By: Anirudha (anirudha81) Date: 2008-08-05 18:34 Message: Logged In: YES user_id=1014478 Originator: NO I have added the necessary test cases and command line options and verified GitInit working.Also All previous test cases have been modified to use Git Init. Please let me know what else you think is remaining. thanks, Ani ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-05 15:00 Message: Logged In: YES user_id=1099750 Originator: NO This feature is still not complete. It should remain open until it is complete. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 09:30:56
|
Feature Requests item #2033472, was opened at 2008-07-31 00:36 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: v0.2.0 (target) >Status: Open Resolution: None >Priority: 8 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Anirudha (anirudha81) Summary: Git Init Initial Comment: Git Init is essential for testing gitclipse. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-05 05:30 Message: Logged In: YES user_id=1099750 Originator: NO This feature is still not complete. It should remain open until it is complete. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 03:43:14
|
Feature Requests item #2033472, was opened at 2008-07-31 10:06 Message generated for change (Settings changed) made by anirudha81 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: v0.2.0 (target) >Status: Closed Resolution: None Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Anirudha (anirudha81) Summary: Git Init Initial Comment: Git Init is essential for testing gitclipse. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2033472&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-05 03:43:14
|
Feature Requests item #2035573, was opened at 2008-08-02 07:51 Message generated for change (Settings changed) made by anirudha81 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2035573&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Website Group: v0.1.0 (target) >Status: Closed Resolution: None Priority: 9 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Anirudha (anirudha81) Summary: Start a "JavaGit Cookbook" Initial Comment: Start a "JavaGit Cookbook" containing cookbook style instructions on how to use the JavaGit Object API and Command API. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089902&aid=2035573&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-04 12:55:11
|
Bugs item #2037398, was opened at 2008-08-04 03:39 Message generated for change (Comment added) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Object API Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Anirudha (anirudha81) Assigned to: Nobody/Anonymous (nobody) Summary: GitAdd in WorkingTree.java does not add files Initial Comment: //Create a new directory to be used as a git repository. repositoryDirectory = FileUtilities.createTempDirectory("Demo_gitRepository"); //Initialize the repository ,similar to git init HelperGitCommands.initRepo(repositoryDirectory); //Create a file in our repository File file = FileUtilities.createFile(repositoryDirectory, "README", "First file in the git repository"); //get the instance of the dotGit Object dotGit = DotGit.getInstance(repositoryDirectory); //get the current working tree from the git repository WorkingTree wt = dotGit.getWorkingTree(); GitAddResponse ar = wt.add(); wt.commitAll("First commit to the git repository"); //Commit fails saying no files added ??? wt.gitADD is not adding files, response object is empty. ---------------------------------------------------------------------- >Comment By: nutans (nutans) Date: 2008-08-04 08:55 Message: Logged In: YES user_id=2152864 Originator: NO Hi Anirudha, Shouldn't GitAddResponse ar = wt.add() be GitAddResponse ar = wt.add(file)? Otherwise, I don't see the file getting added to the repository. ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037398&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-04 03:48:53
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: nutans (nutans) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 23:48 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, Thanks. They look good. Closing. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 22:40 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, The comments are incorporated. Have a look. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 18:28 Message: Logged In: YES user_id=1099750 Originator: YES Closing. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 17:45 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, The comments are incorporated. Have a look. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:33 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, The changes look good. I started a review for the changes and left a comment or two. Please take a look; review Javagit-14. Thanks, James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 11:26 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, I have fixed it. Please confirm and close it. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-04 03:46:53
|
Bugs item #2031803, was opened at 2008-07-29 15:44 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: CLI Implementation >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 9 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Returns Invalid Files Initial Comment: The GitStatusResponse.getUntracked() gives back a list of invalid files. When I have a project in: /home/acase/projects/runtime-EclipseApplication/hello 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 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 ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 23:46 Message: Logged In: YES user_id=1099750 Originator: NO Closing since it is fixed and confirmed. Still hoping to get the reviewed changes in at a later point. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 13:46 Message: Logged In: YES user_id=1099750 Originator: NO Max, Thanks for making the changes. :-) I opened a review for the code and made a few comments. Please take a look at review "Javagit-13". James ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:04 Message: Logged In: YES user_id=2143686 Originator: NO Changed the status to FIXED. ( Fixed By Max ) Hi Max, It's perfectly ok so no worries. ---------------------------------------------------------------------- Comment By: Maxim A. (ma1683) Date: 2008-08-03 11:06 Message: Logged In: YES user_id=2155661 Originator: NO I've modified the CliGitStatus.java to create files with absolute paths, ensuring proper behaviour. I've used CliGitCommit.java as a model. Please verify (svn cange #651). Gurdeep, if you were working on this, I apologize for stepping over your feet... ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:10 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, This seems like a pretty important bug to fix. What is its status? James ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-04 02:40:55
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation >Group: New >Status: Open Resolution: Fixed Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: nutans (nutans) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: nutans (nutans) Date: 2008-08-03 22:40 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, The comments are incorporated. Have a look. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 18:28 Message: Logged In: YES user_id=1099750 Originator: YES Closing. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 17:45 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, The comments are incorporated. Have a look. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:33 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, The changes look good. I started a review for the changes and left a comment or two. Please take a look; review Javagit-14. Thanks, James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 11:26 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, I have fixed it. Please confirm and close it. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 22:30:07
|
Bugs item #2029073, was opened at 2008-07-26 21:22 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Make GitAddOptions optional Initial Comment: I'm wondering if api commands can have optional 'options' when they really are optional. I see it done both ways (git-mv vs. git-add). I would think that if the command line options are options, so should the object paramaters: Can GitAdd provide: public GitAddResponse add(java.io.File repositoryPath, java.io.File file) throws java.io.IOException, JavaGitException as well as public GitAddResponse add(java.io.File repositoryPath, GitAddOptions options, java.io.File file) throws java.io.IOException, JavaGitException Thanks, -- Drew ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 18:30 Message: Logged In: YES user_id=1099750 Originator: NO Closing. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 17:26 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, I finished providing comments on this fix. Please comment in the bug once you have reviewed my comments and committed changes. Thanks, James ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:52 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, What revision did you commit these changes on? Thanks, James ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:46 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:44 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:08 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, Nutan, If one of you can fix this before the build, that would be great. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-07-31 10:37 Message: Logged In: YES user_id=2152864 Originator: NO Gurdeep, Have you done this already(on your machine)? Or, do you want me to assign it to myself and fix the problem? ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 22:16:34
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: None Status: Open Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 18:16 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 18:15 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 18:15 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 16:42 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:59 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:42 Message: Logged In: YES user_id=1099750 Originator: NO Confirming fixed. Marking closed. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 03:54 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:45:17
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: New Status: Open Resolution: Fixed Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: nutans (nutans) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: nutans (nutans) Date: 2008-08-03 17:45 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, The comments are incorporated. Have a look. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:33 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, The changes look good. I started a review for the changes and left a comment or two. Please take a look; review Javagit-14. Thanks, James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 11:26 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, I have fixed it. Please confirm and close it. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:36:42
|
Bugs item #2022986, was opened at 2008-07-20 15:03 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2022986&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: CLI Implementation >Group: v0.1.0 (fixed in) Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Gurdeep Dhindsa (dhindsg) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatus does not output all the modified files Initial Comment: GitStatus output does not generate the list of all the files that have been newly created, deleted or modified if these files are under a subdirectory. e.g. if the repository root is /repo and within repo if there is another directory testdir1, the response object does not show the changes under /repo/testdir1 sub-directory and only shows changes correctly under /repo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2022986&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:36:06
|
Bugs item #2023955, was opened at 2008-07-21 17:20 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2023955&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Test Cases >Group: v0.1.0 (fixed in) Status: Closed Resolution: Fixed Priority: 7 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Anirudha (anirudha81) Summary: Build Tests Fail on Cygwin Initial Comment: I notice that the build seems to fail for me when I run on windows with cygwin and maven. Well actually the build works, but some of the tests fail. I'm attaching the output. ---------------------------------------------------------------------- Comment By: Anirudha (anirudha81) Date: 2008-07-31 00:03 Message: Logged In: YES user_id=1014478 Originator: NO tested on cygwin and mySysGit ---------------------------------------------------------------------- Comment By: Anirudha (anirudha81) Date: 2008-07-30 22:49 Message: Logged In: YES user_id=1014478 Originator: NO All the test are also working on cygwin Except. GitStatusTest. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-07-30 21:31 Message: Logged In: YES user_id=1099750 Originator: NO Andrew, I've changed the resolution to fixed. Once you've tested and verified that it is fixed, please comment that it works for you here. ---------------------------------------------------------------------- Comment By: Anirudha (anirudha81) Date: 2008-07-30 21:03 Message: Logged In: YES user_id=1014478 Originator: NO -- fixed error in creating multiple directories. the CreateFile Method in FileUtilities.java was not closing a file streams due to which JVM was unable to delete files, this explains so why System.gc() was successful. I have removed call to System.gc(). Some test were also failing because of this. ---------------------------------------------------------------------- Comment By: Paul M Bethe (pbethe) Date: 2008-07-30 17:02 Message: Logged In: YES user_id=308431 Originator: NO Having installed mysgit, there are still one directory created: GitLogTestRepo and a few failures... Failed tests: testSingleGitFile(edu.nyu.cs.javagit.api.TestGitFileSystem) testGitFileSystem(edu.nyu.cs.javagit.api.TestGitFileSystem) testGitMvErrorResponse(edu.nyu.cs.javagit.api.commands.TestGitMvResponse) testModifiedNotUpdatedFiles(edu.nyu.cs.javagit.api.commands.TestGitStatus) Tests in error: testRename(edu.nyu.cs.javagit.api.commands.TestGitMv) testMove(edu.nyu.cs.javagit.api.commands.TestGitMv) Tests run: 91, Failures: 4, Errors: 2, Skipped: 0 ---------------------------------------------------------------------- Comment By: Paul M Bethe (pbethe) Date: 2008-07-29 20:52 Message: Logged In: YES user_id=308431 Originator: NO the problem is the '/' versus '\' in the file paths. install http://code.google.com/p/msysgit/ and put that in your path ahead of the cygwin installed git. ---------------------------------------------------------------------- Comment By: Andrew Case (andrewcase) Date: 2008-07-21 17:56 Message: Logged In: YES user_id=2143267 Originator: YES Also... it creates all the test directories directly in C:\. So I have: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\WINDOWS\system32>cd .. C:\WINDOWS>cd .. C:\>dir Volume in drive C has no label. Volume Serial Number is 0031-17B1 Directory of C:\ 04/11/2008 04:48 PM 0 AUTOEXEC.BAT 04/11/2008 04:48 PM 0 CONFIG.SYS 06/12/2008 10:52 PM <DIR> cygwin 04/11/2008 07:05 PM <DIR> dell 05/03/2008 07:40 PM <DIR> Documents and Settings 07/21/2008 03:51 PM <DIR> GitBranchTestRepo 07/21/2008 03:51 PM <DIR> GitBranchTestRepo0 07/21/2008 03:51 PM <DIR> GitBranchTestRepo1 07/21/2008 03:54 PM <DIR> GitBranchTestRepo10 07/21/2008 03:54 PM <DIR> GitBranchTestRepo11 07/21/2008 03:54 PM <DIR> GitBranchTestRepo12 07/21/2008 03:54 PM <DIR> GitBranchTestRepo13 07/21/2008 03:54 PM <DIR> GitBranchTestRepo14 07/21/2008 03:54 PM <DIR> GitBranchTestRepo15 07/21/2008 03:54 PM <DIR> GitBranchTestRepo16 07/21/2008 03:54 PM <DIR> GitBranchTestRepo17 07/21/2008 04:05 PM <DIR> GitBranchTestRepo18 07/21/2008 04:05 PM <DIR> GitBranchTestRepo19 07/21/2008 03:51 PM <DIR> GitBranchTestRepo2 07/21/2008 04:05 PM <DIR> GitBranchTestRepo20 07/21/2008 04:05 PM <DIR> GitBranchTestRepo21 07/21/2008 04:05 PM <DIR> GitBranchTestRepo22 07/21/2008 04:05 PM <DIR> GitBranchTestRepo23 07/21/2008 04:05 PM <DIR> GitBranchTestRepo24 07/21/2008 04:05 PM <DIR> GitBranchTestRepo25 07/21/2008 04:06 PM <DIR> GitBranchTestRepo26 07/21/2008 04:06 PM <DIR> GitBranchTestRepo27 07/21/2008 04:06 PM <DIR> GitBranchTestRepo28 07/21/2008 04:06 PM <DIR> GitBranchTestRepo29 07/21/2008 03:51 PM <DIR> GitBranchTestRepo3 07/21/2008 04:06 PM <DIR> GitBranchTestRepo30 07/21/2008 04:06 PM <DIR> GitBranchTestRepo31 07/21/2008 04:06 PM <DIR> GitBranchTestRepo32 07/21/2008 04:06 PM <DIR> GitBranchTestRepo33 07/21/2008 04:12 PM <DIR> GitBranchTestRepo34 07/21/2008 04:12 PM <DIR> GitBranchTestRepo35 07/21/2008 04:12 PM <DIR> GitBranchTestRepo36 07/21/2008 04:12 PM <DIR> GitBranchTestRepo37 07/21/2008 04:12 PM <DIR> GitBranchTestRepo38 07/21/2008 04:12 PM <DIR> GitBranchTestRepo39 07/21/2008 03:51 PM <DIR> GitBranchTestRepo4 07/21/2008 04:12 PM <DIR> GitBranchTestRepo40 07/21/2008 04:12 PM <DIR> GitBranchTestRepo41 07/21/2008 03:51 PM <DIR> GitBranchTestRepo5 07/21/2008 03:53 PM <DIR> GitBranchTestRepo6 07/21/2008 03:53 PM <DIR> GitBranchTestRepo7 07/21/2008 03:54 PM <DIR> GitBranchTestRepo8 07/21/2008 03:54 PM <DIR> GitBranchTestRepo9 07/21/2008 03:51 PM <DIR> GitCheckoutTestRepository 07/21/2008 03:51 PM <DIR> GitCheckoutTestRepository0 07/21/2008 03:51 PM <DIR> GitCheckoutTestRepository1 07/21/2008 04:05 PM <DIR> GitCheckoutTestRepository10 07/21/2008 04:06 PM <DIR> GitCheckoutTestRepository11 07/21/2008 04:06 PM <DIR> GitCheckoutTestRepository12 07/21/2008 04:06 PM <DIR> GitCheckoutTestRepository13 07/21/2008 04:12 PM <DIR> GitCheckoutTestRepository14 07/21/2008 04:12 PM <DIR> GitCheckoutTestRepository15 07/21/2008 04:12 PM <DIR> GitCheckoutTestRepository16 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository2 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository3 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository4 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository5 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository6 07/21/2008 03:54 PM <DIR> GitCheckoutTestRepository7 07/21/2008 04:05 PM <DIR> GitCheckoutTestRepository8 07/21/2008 04:05 PM <DIR> GitCheckoutTestRepository9 07/21/2008 03:51 PM <DIR> GitCommitTestRepo 07/21/2008 03:51 PM <DIR> GitCommitTestRepo0 07/21/2008 03:54 PM <DIR> GitCommitTestRepo1 07/21/2008 04:12 PM <DIR> GitCommitTestRepo10 07/21/2008 03:54 PM <DIR> GitCommitTestRepo2 07/21/2008 03:54 PM <DIR> GitCommitTestRepo3 07/21/2008 03:54 PM <DIR> GitCommitTestRepo4 07/21/2008 04:05 PM <DIR> GitCommitTestRepo5 07/21/2008 04:05 PM <DIR> GitCommitTestRepo6 07/21/2008 04:07 PM <DIR> GitCommitTestRepo7 07/21/2008 04:07 PM <DIR> GitCommitTestRepo8 07/21/2008 04:12 PM <DIR> GitCommitTestRepo9 07/21/2008 03:51 PM <DIR> GitFileSystemTest 07/21/2008 03:51 PM <DIR> GitFileSystemTest0 07/21/2008 03:54 PM <DIR> GitFileSystemTest1 07/21/2008 04:12 PM <DIR> GitFileSystemTest10 07/21/2008 03:54 PM <DIR> GitFileSystemTest2 07/21/2008 03:54 PM <DIR> GitFileSystemTest3 07/21/2008 03:54 PM <DIR> GitFileSystemTest4 07/21/2008 04:05 PM <DIR> GitFileSystemTest5 07/21/2008 04:05 PM <DIR> GitFileSystemTest6 07/21/2008 04:07 PM <DIR> GitFileSystemTest7 07/21/2008 04:07 PM <DIR> GitFileSystemTest8 07/21/2008 04:12 PM <DIR> GitFileSystemTest9 07/21/2008 03:51 PM <DIR> GitMvTestResponseRepo 07/21/2008 03:51 PM <DIR> GitMvTestResponseRepo0 07/21/2008 03:54 PM <DIR> GitMvTestResponseRepo1 07/21/2008 03:54 PM <DIR> GitMvTestResponseRepo2 07/21/2008 03:54 PM <DIR> GitMvTestResponseRepo3 07/21/2008 03:54 PM <DIR> GitMvTestResponseRepo4 07/21/2008 03:51 PM <DIR> GitStatusTestRepository 07/21/2008 03:51 PM <DIR> GitStatusTestRepository0 07/21/2008 03:51 PM <DIR> GitStatusTestRepository1 07/21/2008 03:54 PM <DIR> GitStatusTestRepository10 07/21/2008 03:54 PM <DIR> GitStatusTestRepository11 07/21/2008 03:54 PM <DIR> GitStatusTestRepository12 07/21/2008 03:54 PM <DIR> GitStatusTestRepository13 07/21/2008 03:54 PM <DIR> GitStatusTestRepository14 07/21/2008 03:54 PM <DIR> GitStatusTestRepository15 07/21/2008 03:54 PM <DIR> GitStatusTestRepository16 07/21/2008 04:05 PM <DIR> GitStatusTestRepository17 07/21/2008 04:05 PM <DIR> GitStatusTestRepository18 07/21/2008 04:05 PM <DIR> GitStatusTestRepository19 07/21/2008 03:51 PM <DIR> GitStatusTestRepository2 07/21/2008 04:05 PM <DIR> GitStatusTestRepository20 07/21/2008 04:05 PM <DIR> GitStatusTestRepository21 07/21/2008 04:05 PM <DIR> GitStatusTestRepository22 07/21/2008 04:07 PM <DIR> GitStatusTestRepository23 07/21/2008 04:07 PM <DIR> GitStatusTestRepository24 07/21/2008 04:07 PM <DIR> GitStatusTestRepository25 07/21/2008 04:07 PM <DIR> GitStatusTestRepository26 07/21/2008 04:07 PM <DIR> GitStatusTestRepository27 07/21/2008 04:12 PM <DIR> GitStatusTestRepository28 07/21/2008 04:12 PM <DIR> GitStatusTestRepository29 07/21/2008 03:51 PM <DIR> GitStatusTestRepository3 07/21/2008 04:12 PM <DIR> GitStatusTestRepository30 07/21/2008 04:12 PM <DIR> GitStatusTestRepository31 07/21/2008 04:12 PM <DIR> GitStatusTestRepository32 07/21/2008 04:12 PM <DIR> GitStatusTestRepository33 07/21/2008 03:51 PM <DIR> GitStatusTestRepository4 07/21/2008 03:54 PM <DIR> GitStatusTestRepository5 07/21/2008 03:54 PM <DIR> GitStatusTestRepository6 07/21/2008 03:54 PM <DIR> GitStatusTestRepository7 07/21/2008 03:54 PM <DIR> GitStatusTestRepository8 07/21/2008 03:54 PM <DIR> GitStatusTestRepository9 04/11/2008 07:06 PM <DIR> Intel 07/17/2008 05:48 PM <DIR> jdk1.6.0_06 07/17/2008 06:14 PM <DIR> Program Files 07/19/2008 07:48 PM <DIR> projects 07/21/2008 12:52 AM <DIR> WINDOWS 2 File(s) 0 bytes 134 Dir(s) 19,222,142,976 bytes free C:\> Not very friendly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2023955&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:35:39
|
Bugs item #2031698, was opened at 2008-07-29 13:46 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031698&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Misc >Group: v0.1.0 (fixed in) Status: Closed Resolution: Fixed Priority: 7 Private: No Submitted By: Paul M Bethe (pbethe) Assigned to: nutans (nutans) Summary: Tests fail on Linux Initial Comment: Failed tests: testGitMvInvalidResponse(edu.nyu.cs.javagit.api.commands.TestGitMvResponse) Tests run: 90, Failures: 1, Errors: 0, Skipped: 0 running on SUSE Linux. also stray folders in tmp are left undeleted: > ls -ltrd /tmp/Git* drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository0 drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository1 drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository2 drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository3 drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository4 drwxrwxr-x 4 pbethe fis 4096 2008-07-29 13:18 /tmp/GitStatusTestRepository5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031698&group_id=233450 |