Thanks for the explanation, that helped me to understand it but not
completely. So, what do you actually mean by "inspect the state of a
I take methods provided by you:
And here are some more suggestions to help inspect the state of a project:
Would that be enough?
I guess, I don't understand the use cases for the GitFacet yet.
Who is going to use it and what are the potential scenarios? The git
undo plugin will require a lot more than that. And I assume that
GitFacet is not really a wrapper for the jGit functionality.
On 04/20/2012 06:00 PM, forge-dev-request(a)lists.jboss.org wrote:
> Message: 5
> Date: Fri, 20 Apr 2012 09:21:10 -0400
> From: "Lincoln Baxter, III"<lincolnbaxter(a)gmail.com>
> Subject: Re: [forge-dev] GitPlugin Facet
> To: forge-dev List<forge-dev(a)lists.jboss.org>
> Content-Type: text/plain; charset="iso-8859-1"
> Hey Jevgeni,
> 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.
> GitFacet (as the issue describes poorly) is something that should be usable
> to inspect the state of a Project via:
> After that, everything else is an added benefit. It should probably also
> perform tasks like:
> And that's where your imagination kicks in.
> Does that make sense?
Hi Forge Developers,
I am interested in the forge project, especially in git-related
functionality. I am a CS student and I submitted a proposal to this
year's google summer of code to implement a git powered undo
functionality in forge, as mentioned in the FORGE-320 issue. Even though
accepted proposals will be announced on Monday, April 23rd, I decided to
dive into forge source code.
A good starting point recommended by Lincoln, was FORGE-183. I created a
git facet in the forge core project, under
'git-tools\src\main\java\org.jboss.forge.git\GitFacet' but I guess that
is not the best place for it.
Lincoln, you mentioned splitting the plugin in two parts. Could you
please provide more details?
Guys, if you have any ideas related to either FORGE-320 or FORGE-183,
please let me know.
I will add ideas from my gsoc proposal into the FORGE-320 after the
announcement on Monday.
You may notice when building forge from master, that test output is no
longer printed to the console. This is because George Gastaldi has
implemented a long standing feature request:
It is now possible to call: getOutput() in Forge test cases extending from
AbstractShellTest, making assertions on what your plugin is actually
printing to the console.
Lincoln Baxter, III
"Simpler is better."
I noticed that there are some branches in
https://github.com/forge/core/ that could be deleted as well (Eg:
feature/FORGE-399, FORGE-458 ).
Is there anyone working on that ? Can you guys clean it up if that´s ok ?
Just created a new issue (https://issues.jboss.org/browse/FORGE-541)
regarding i18n support on Forge enabled projects.
I was thinking if it should it be part of Forge core. WDYT ?
Feel free to add any new comment on this issue. I plan to start
working on it still this week.