April 2012 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-156) Update MetaWidget dependencies to not bring in metawidget-all

by Andrew Rubinger (JIRA)

Update MetaWidget dependencies to not bring in metawidget-all ------------------------------------------------------------- Key: SEAMFORGE-156 URL: https://issues.jboss.org/browse/SEAMFORGE-156 Project: Seam Forge Issue Type: Task Reporter: Andrew Rubinger Fix For: 1.0.0.Alpha4 We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 11 months

8
17
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

10 years, 3 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."

10 years, 3 months

3
7
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.

10 years, 3 months

4
8
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

10 years, 3 months

2
3
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev April 2012