August 2011 - 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

12 years, 3 months

8
17
0 / 0

Important changes to Forge API and packaging

by Lincoln Baxter, III

FYI. 1. I've modified XMLParser to return org.jboss.forge.parser.xml.Node instead of Shrinkwrap Nodes - Plugins will need to be updated. 2. I've moved forge/modules-build/ back to dist/ (forge-distribution) -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 3 months

2
5
0 / 0

Re: [forge-dev] Lincoln's Side Job?

by Rodney Russ

Ha ... that's awesome. "At Lincoln we believe that in order to provide the highest quality forgings we must work hand in hand with our customers and we must embrace change. This is why since 1962, we have lived by our motto; Forging Partnerships for Tomorrow's Needs." New tagline, "Forging plugins for tomorrow's applications" ----- "Koen Aers" <koen.aers(a)gmail.com> wrote: > From: "Koen Aers" <koen.aers(a)gmail.com> > To: "forge-dev List" <forge-dev(a)lists.jboss.org> > Sent: Friday, August 26, 2011 2:55:13 AM GMT -07:00 US/Canada Mountain > Subject: [forge-dev] Lincoln's Side Job? > > I stumbled across this one by accident: http://www.lincolnforge.com/ > > > Cheers, > Koen > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev

13 years, 4 months

4
4
0 / 0

Lincoln's Side Job?

by Koen Aers

I stumbled across this one by accident: http://www.lincolnforge.com/ Cheers, Koen

13 years, 4 months

1
0
0 / 0

Seam 2 -> Seam 3 Migration Strategy

by Lincoln Baxter, III

Hi Guys, I'd like to start implementing a Seam 2 -> Seam 3 plugin for Forge, so that we can give people *Something* to get started with this process. My vision at this point is to specify a list of tasks for the plugin to perform, E.g. - Updating the POM to include new dependencies - Replacing Seam 2 annotations with Seam 3 annotations - Getting basic configuration files set up - Doing some static code analysis in order to print a list of tasks that need to be done by hand (sort of a "what do I have left?") In order to accomplish this, having *never* used Seam 2, I need a few things: 1. A list of APIs and which Seam 3 feature replaces it - this includes annotations, static classes, and injected interfaces/classes. 2. A test project with all of these features (or at least a lot of them.) As soon as I have these things, I will get started, and anyone who wants to help out and work on this as well is more than welcome to join me! -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 4 months

5
8
0 / 0

Forge 1.0.0.Beta1 Released

by Lincoln Baxter, III

http://twitter.com/#!/lincolnthree/status/101725675945336832 https://docs.jboss.org/author/display/SEAMFORGE/Home Enjoy! -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 4 months

1
0
0 / 0

Planning to release Forge 1.0.0.Beta1 today if possible.

by Lincoln Baxter, III

If there are any major outstanding issues, please let me know! Sorry for the short notice. Releases should be happening more frequently now, and I will provide a warning a week or so beforehand. -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 4 months

1
0
0 / 0

Forge Issues List has been created (Please Subscribe)

by Lincoln Baxter, III

To make filtering JIRA issues for Forge easier, I've created https://lists.jboss.org/mailman/listinfo/forge-issues Please sign up to receive notifications of JIRA events. Thanks, -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-263) Add the possibility to register TriggeredActions on the ConsoleReader

by Koen Aers (JIRA)

Add the possibility to register TriggeredActions on the ConsoleReader --------------------------------------------------------------------- Key: SEAMFORGE-263 URL: https://issues.jboss.org/browse/SEAMFORGE-263 Project: Seam Forge Issue Type: Feature Request Reporter: Koen Aers This issue is related to SEAMFORGE-253. Using the CommandInterceptor does not give me the wanted result as it relies on the ConsoleReader mechanism to read entire lines. I have had better results with using the ConsoleReader ability to register so-called TriggeredActions. These TriggeredActions are simple ActionListeners that get performed when a particular character is read. The Forge API needs to include a new interface in the SPI package and the ShellImpl needs to register the beans implementing this interface during the setup of the ConsoleReader. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-113) project list-dependencies should resolve property values

by Dan Allen (JIRA)

project list-dependencies should resolve property values -------------------------------------------------------- Key: SEAMFORGE-113 URL: https://issues.jboss.org/browse/SEAMFORGE-113 Project: Seam Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Priority: Minor Currently, when you list dependencies, it shows the property expression rather than the actual version in the case a property expression is used: {code} org.jboss.arquillian : arquillian-junit : ${arquillian.version} : jar : test {code} In this case, both the property and the version should be shown: {code} org.jboss.arquillian : arquillian-junit : ${arquillian.version} = 1.0.0.Alpha5 : jar : test {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev August 2011