From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
To: git@vger.kernel.org
Subject: Re: Newbie questions regarding jgit
Date: Wed, 12 Nov 2008 12:56:20 -0500 [thread overview]
Message-ID: <491B18C4.2070000@wellfleetsoftware.com> (raw)
In-Reply-To: <491AE91C.4020402@wellfleetsoftware.com>
So far I have figured out how to get the treeWalk for the path filter as
shown below.
Now I am lost as to how to get the blob associated with the treeWalk.
TIA for your help.
/**
* Gets the content of specified file in git Repo.
*
* @parameter relativePath the relative path in jitRepo for desired
file to get
* @parameter versionName the versionName for the desired file. It
will be unmarshalled from String to ObjectId.
* @return the content of the desired file version packaged as a
DataHandler.
*/
public DataHandler get(String relativePath, String versionName)
throws RepositoryException {
ObjectId retrieveStart = repository.resolve(versionName);
RevWalk revWalk = new RevWalk(repository);
RevCommit entry = revWalk.parseCommit(retrieveStart);
RevTree revTree = entry.getTree();
TreeWalk treeWalk = TreeWalk.forPath(repository,
relativePath, revTree);
//Not sure how to get the blob next
}
Farrukh Najmi wrote:
....
> For my immediate needs, I need to implement a GitRepository class with
> two methods using gjit as shown below. I would appreciate any guidance
> and pseudo-code examples on how to implement these methods. Please
> keep in mind that I am just getting to know git itself and gjit was
> key to my considering git over Mercurial and other distributed VCSs.
>
> public class GitRepositoryManager {
>
> Repository gitRepo;
>
> ...
>
> /**
> * Gets the content of specified file in git Repo.
> *
> * @parameter relativePath the relative path in jitRepo for
> desired file to get
> * @parameter versionName the versionName for the desired file. It
> will be unmarshalled from String to ObjectId.
> * @return the content of the desired file version packaged as a
> DataHandler.
> */
> public DataHandler get(String relativePath, String versionName)
> throws RepositoryException {
> DataHandler dh = null;
>
> ...
> return dh;
> }
>
> /**
> * Creates a new version of specified version of file in git Repo.
> *
> * @parameter relativePath the relative path in jitRepo for
> desired file to get
> * @parameter versionName the versionName for the desired file. It
> will be unmarshalled from String to ObjectId.
> * @parameter content the content of the new version for specified
> file packaged as a DataHandler.
> */
> public void update(String relativePath, String versionName,
> DataHandler content) throws RepositoryException {
> ...
> }
>
> }
>
> Farrukh Najmi wrote:
>> Jonas Fonseca wrote:
>> ...
>>>
>>>> Now I am wondering where to begin to learn how to do the equivalent
>>>> of the
>>>> following commands via the gjit Java API:
>>>>
>>>> * git add /file/
>>>> * git rm /file/
>>>> * git mv /file
>>>> * Whatever is the git way to get a specific version of a file
>>>>
>>>
>>> JGit currently has two APIs for working with the index, which will
>>> allow you to add, remove and move data around in the tree. In nbgit I
>>> ended up using GitIndex, which I found easier to figure out. As I
>>> understand it, in the long run you want to use the DirCache API, but
>>> it is still a work in progress.
>>>
>>
>> I am happy to use GitIndex now and switch to DirCache API later when
>> it is ready.
>> Can I please get some pseudo-code fragments on how to do the use
>> cases I identified above?
>> The javadoc is still not obvious to me.
>>>
>>>> I am hoping that there aremore docs, samples, tutorials etc.
>>>> somewhere that
>>>> I am missing. Thanks for any help you can provide. Some pointers or
>>>> code
>>>> fragments would be terrific.
>>>>
>>>
>>> I started working on a tutorial for JGit, but didn't get very far so
>>> it mostly consists of stub pages.
>>>
>>> - http://code.google.com/docreader/#p=egit&s=egit&t=JGitTutorial
>>>
>>> I have been working on moving the tutorial to maven project before
>>> starting to write the more code heavy topics. This would make it
>>> possible to include code snippets in the tutorial, while also allowing
>>> to compile and test the examples.
>>>
>>
>> The wiki is an awesome resource even in its current state. Thank you.
>> I would be glad to help contribute improvements to wiki if you give me
>> write privilege. What I could do is take the help I get from the list
>> and
>> then update wiki carefully as appropriate if you want me to help.
>>
>> Thanks again to all of you for helping get me bootstrapped with gjit
>> and git.
>>
>
>
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
next prev parent reply other threads:[~2008-11-12 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:44 Newbie questions regarding jgit Farrukh Najmi
2008-11-11 21:12 ` Farrukh Najmi
2008-11-11 21:37 ` Jonas Fonseca
2008-11-11 21:44 ` Shawn O. Pearce
2008-11-11 22:01 ` Jonas Fonseca
2008-11-11 23:11 ` Shawn O. Pearce
2008-11-11 23:48 ` [PATCH] Add maven distribution management info for the new snapshot repository Jonas Fonseca
2008-11-12 0:58 ` Shawn O. Pearce
2008-11-12 1:01 ` Shawn O. Pearce
2008-11-12 2:24 ` Newbie questions regarding jgit Imran M Yousuf
2008-11-12 12:51 ` Farrukh Najmi
2008-11-12 14:05 ` Farrukh Najmi
2008-11-12 14:33 ` Farrukh Najmi
2008-11-12 17:56 ` Farrukh Najmi [this message]
2008-11-12 18:30 ` Jonas Fonseca
2008-11-12 19:29 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2008-11-12 22:36 Robin Rosenberg
2008-11-12 22:37 Robin Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491B18C4.2070000@wellfleetsoftware.com \
--to=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).