Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JGit GSoc 2012"

(added project timeline)
m (Phase 1 (up to June 20, 2012))
Line 19: Line 19:
  
 
Goals:  
 
Goals:  
 +
 +
*Research JGIT CLI code base - '''Complete'''
 +
*Compile list of commands to update in this project - '''In progress'''
 +
*Write script to automate comparison of JGit API and JGit CLI - '''In progress'''
  
*Research JGIT CLI code base
+
Note: Phase 1 was extended to June 20 to some initial problems with set up, and overestimating available work time during travels.
*Compile list of commands to update in this project
+
*Write script to automate comparison of JGit API and JGit CLI
+
 
+
Note: Phase 1 was extended to June 20 to some initial problems with set up, and overestimating available work time during travels.  
+
  
 
===Phase 2 (up to July 10, 2012) ===
 
===Phase 2 (up to July 10, 2012) ===

Revision as of 13:07, 17 June 2012

JGit Command Line Interface

About

The Command Line Interface (CLI) in JGit mimics its CGit equivalent. However, there is more to it than just having a second tool doing the same thing. The JGit CLI is a perfect way to verify robustness of the JGit Command API. It can be also used to simplify writing JUnit tests.

The project would be about adding new CLI commands to the o.e.jgit.pgm project and vice versa ie translating some of the existing CLI commands/switches to JGit Command API. In addition, the student could help with randomized JGit tests.

Project timeline

Phase 1 (up to June 20, 2012)

Goals:

  • Research JGIT CLI code base - Complete
  • Compile list of commands to update in this project - In progress
  • Write script to automate comparison of JGit API and JGit CLI - In progress

Note: Phase 1 was extended to June 20 to some initial problems with set up, and overestimating available work time during travels.

Phase 2 (up to July 10, 2012)

Goals:

  • Implement first commands
  • Research automated and unit testing in JGIT

Some steps have been taken for Phase 2, including:

  • Submitting bug reports to learn to use Bugzilla [1]
  • Submitting trivial bug patch to learn to use Gerrit [2]

Phase 3 (up to August 10, 2012)

-

Resources

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=382163 [2] https://git.eclipse.org/r/#/c/6102/

Back to the top