May 2012 - forge-dev - Jboss List Archives

by George Gastaldi (via Doodle)

George Gastaldi (gegastaldi(a)gmail.com) invites you to participate in the Doodle poll "Forge Hack Night". Follow this link to open the poll: http://www.doodle.com/t92c5ic9v2u29e7h

12 years, 6 months

2
1
0 / 0

reference work for git-based undo plugin

by Dan Allen

Jevgeni, I came across some code last week that may prove to be a useful reference for the git-based undo functionality you are working on for Forge. The Aquillian OpenShift container adapter uses a temporary git repository to stage the project in order to push it to a separate remote location where the tests are run. What you might find useful about this plugin is the use of jgit and the synchronization of state from the current repository to the temporary repository. Here's the main class involved: https://github.com/arquillian/arquillian-container-openshift/blob/master/... Here's where it is invoked: https://github.com/arquillian/arquillian-container-openshift/blob/master/... Perhaps it will provide some useful ideas. -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://google.com/profiles/dan.j.allen http://mojavelinux.com http://mojavelinux.com/seaminaction

12 years, 6 months

1
0
0 / 0

Forge Hack Night

by George Gastaldi

Hello everyone ! We should have a Forge Hack Night sometime to focus on the nasty bugs and shorten the release cycle. That´s the same activity people from Seam 3 had. WDYT ? Regards, George Gastaldi

12 years, 6 months

5
6
0 / 0

Packaging and installing plugins from Maven

by Lincoln Baxter, III

Hey Keith! Regarding instaling plugins from Maven - we'd definitely like to support this. Perhaps we could take what you've done and standardize it as a supported plugin installation mechanism? Regarding testing the plugins in a forge release distribution. As of Forge 1.0.3.Final, you can invoke Forge from the command line using: forge -e "command or script to run" So hopefully that will be of use :) You can install plugins using this feature as well, so with the combination of the two, we should have some good testing options! -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

12 years, 6 months

3
7
0 / 0

FORGE-550: list-scaffold-providers

by George Gastaldi

Hello all, I´ve implemented the plugin specified on https://issues.jboss.org/browse/FORGE-550, however, there is a small change on the actual scaffold providers: You must add the @Help annotation on top of it so that it will be displayed next to the alias when running this plugin. I kindly ask you if you are working on a scaffold provider to add this annotation so it should display properly when running "list-scaffold-providers" Pull request @ https://github.com/forge/core/pull/153 Regards, George Gastaldi

12 years, 6 months

2
3
0 / 0

GitHub: question on synchronization with master repository

by Thomas Frühbeck

Hi, after having a look at receipt at http://forge.github.com/docs/get_involved/contribute.html I would like to clarify the use the repositories. - I have cloned forge/core to a private github repository - cloned my repository to my local system - generated a branch, committed changes, pushed to my github repository All OK. One thing is left: how will I get updates of the master forge/core into my _remote_ repository, as there is no "pull" on github? If I understood correctly, I can associate the remote master by "git remote add upstream <git_master_repo>" To get the changes of the "upstream" master I issued: ~> git pull upstream master Now my local repository was up do date, but not my remote repository. So I issued: ~> git push which seemed to update my private _remote_ repository with the changes from the remote "upstream" master. So for me this means, that from now on I "remote control" my private _remote_ repository via my _local_ repo. Could you kindly comment/confirm/explain in more detail. Thanks, Thomas

12 years, 6 months

5
4
0 / 0

Some incorrect changes to JSF scaffolding?

by Richard Kennard

Hi guys, I'm taking a break from the JSF UI scaffolding at the moment, but I notice some incorrect changes have been made. Could I please ask someone to revisit them? Specifically: 1. ForgeInspector now holds a reference to ForgeInspectorConfig internally, and uses this to access certain settings. Because ForgeInspector is required to be immutable, but ForgeInspectorConfig is not, this may break things. ForgeInspector should *defensively copy* any settings it needs at construction time. 2. ForgeInspectorConfig has a getProject method that doesn't appear to be used? 3. ForgeInspectionResultProcessor has a setProject method. Again, this breaks immutability. Also, it doesn't appear to be used? Regards, Richard.

12 years, 6 months

4
8
0 / 0

Re: [forge-dev] GSoC 2012!

by Lincoln Baxter, III

Hi Jevgeni, Thanks for letting me know about your vacation. Have fun! I've copied the dev list, because this should be discussed openly among all the community :) Answers in line: What methods should the GitFacet implement (or at least provide stubs for) > for the FORGE-183 to get accepted? I'll answer this with another question: "what is the minimal set of Git operations that will make it useful?" We can always expand later. So I'd suggest starting with the bare minimum. Should GitUtils be a part of FORGE-183 as well? > Not sure what you mean? If you need to make changes to GitUtils to implement FORGE-183, then sure, that's fine. What methods should I add in there (everything from Git)? Start with the basics. I recommend starting with what you think is necessary to implement the UNDO features :) > In the mailing list I identified 5 methods. Can I use GitUtils class which > is already present in the project? ( > > https://github.com/forge/core/blob/master/git-tools/src/main/java/org/jbo... > ) Yes, that would be my suggestion. If I add all the methods needed for the undo plugin (about 15), > wouldn't it be a pretty big commit for a single JIRA issue? > Size of commit is not really important as long as the JIRA issue is clear. If you think the Issue is too vague, then feel free to split it into several issues. Do you have permissions to edit and create JIRA issues? If not, let me know and I will grant it to you. Thanks~! Good questions! Always ask :) Lincoln

12 years, 6 months

1
0
0 / 0

Forge Arquillian plugin guide on arquillian.org

by Dan Allen

I just finished revising the "Get Started Faster with Forge" guide on arquillian.org to be current with the latest final releases of Forge and Arquillian. It should now work as expected. http://arquillian.org/guides/get_started_faster_with_forge/ There's no question, the Forge Arquillian plugin is the fastest way to get an Arquillian project setup and churn out tests. Conversely, this guide--and subsequent guides--could bring a lot of exposure to the Forge project. It would be great if the Forge team kept an eye on this tutorial to make sure that it remains current. As a basic step, simply report problems in the issue tracker when you hear about them (or encourage others to do so). https://github.com/arquillian/arquillian.github.com/issues Even better, correct the file and send a pull request when you see something out of date. Also, feel free to spread the word about the guide! Thanks! -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://google.com/profiles/dan.j.allen http://mojavelinux.com http://mojavelinux.com/seaminaction

12 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev May 2012