Hey Jevgeni,<br><br>Welcome!<br><br>Regarding the GitFacet - I believe it's in the right place for the moment, but I don't believe that the GitPlugin should be referencing it, since the commands in GitPlugin could be used even without a Project. <br>
<br>GitFacet (as the issue describes poorly) is something that should be usable to inspect the state of a Project via:<br><br><span style="font-family:courier new,monospace">project.hasFacet(GitFacet.class)</span><br><br>
After that, everything else is an added benefit. It should probably also perform tasks like:<br><br><span style="font-family:courier new,monospace">project.getFacet(GitFacet.class).getBranches()</span><br>
<span style="font-family:courier new,monospace">project.getFacet(GitFacet.class).getTags()</span><br>
<span style="font-family:courier new,monospace">project.getFacet(GitFacet.class).getRemotes()</span><br>
<span style="font-family:courier new,monospace">project.getFacet(GitFacet.class).getStatus()</span><br><br>And that's where your imagination kicks in.<br><br>Does that make sense?<br><br>~Lincoln<br><br><div class="gmail_quote">
On Thu, Apr 19, 2012 at 3:59 PM, Jevgeni Zelenkov <span dir="ltr"><<a href="mailto:jevgeni.zelenkov@googlemail.com">jevgeni.zelenkov@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Forge Developers,<br>
<br>
I am interested in the forge project, especially in git-related<br>
functionality. I am a CS student and I submitted a proposal to this<br>
year's google summer of code to implement a git powered undo<br>
functionality in forge, as mentioned in the FORGE-320 issue. Even though<br>
accepted proposals will be announced on Monday, April 23rd, I decided to<br>
dive into forge source code.<br>
<br>
A good starting point recommended by Lincoln, was FORGE-183. I created a<br>
git facet in the forge core project, under<br>
'git-tools\src\main\java\org.jboss.forge.git\GitFacet' but I guess that<br>
is not the best place for it.<br>
<br>
Lincoln, you mentioned splitting the plugin in two parts. Could you<br>
please provide more details?<br>
<br>
Guys, if you have any ideas related to either FORGE-320 or FORGE-183,<br>
please let me know.<br>
<br>
Best regards,<br>
Jevgeni Zelenkov<br>
<br>
<br>
P.S.<br>
I will add ideas from my gsoc proposal into the FORGE-320 after the<br>
announcement on Monday.<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."<br>