June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-957: ---------------------------------------- Summary: Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs Key: FORGE-957 URL: https://issues.jboss.org/browse/FORGE-957 Project: Forge Issue Type: Feature Request Affects Versions: 2.0.0.Alpha5 Reporter: Lincoln Baxter III Fix For: 2.x Future This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-956) Resources API should support hiding path prefixes extensibly

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-956: ---------------------------------------- Summary: Resources API should support hiding path prefixes extensibly Key: FORGE-956 URL: https://issues.jboss.org/browse/FORGE-956 Project: Forge Issue Type: Feature Request Components: Plugin Repository, UI - Eclipse Affects Versions: 2.0.0.Alpha5 Reporter: Lincoln Baxter III Fix For: 2.x Future When working in Eclipse, users do not want to see full file paths if paths are children of the current eclipse workspace. These paths should be displayed as relative paths instead of fully qualified filesystem paths. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-85: --------------------------------- Fix Version/s: 1.x Future (was: 2.x Future) > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Labels: HackNight > Fix For: 1.x Future > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-85: --------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Labels: HackNight > Fix For: 2.x Future > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-184) Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-184?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-184: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-184 > URL: https://issues.jboss.org/browse/FORGE-184 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins, Plugin Repository > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Forge should provide commands to simplify the process of registering a plugin with the central repository. > The command should verify all metadata by attempting to build/install the plugin before allowing an update request to be sent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-186) Allow decoration/interception of Plugin output

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-186?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-186: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Allow decoration/interception of Plugin output > ---------------------------------------------- > > Key: FORGE-186 > URL: https://issues.jboss.org/browse/FORGE-186 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Usability > Affects Versions: 1.0.6.Final > Reporter: Jonathan Fuerth > Priority: Minor > Fix For: 2.x Future > > > The Java syntax highlighting in cat & less output is wonderful. As much as we all (don't) love XML, there's still a lot of it to deal with in Java EE projects. Syntax highlighting can help. > Allowing decoration of plugin output would be a major win for extensibility and modularity here. Allowing individual plugins to separate concerns based on runtime conditions. (E.g, what type of resource is in scope.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-162) Reload the current project/resource metadata when filesystem changes occur

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-162?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-162: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Reload the current project/resource metadata when filesystem changes occur > -------------------------------------------------------------------------- > > Key: FORGE-162 > URL: https://issues.jboss.org/browse/FORGE-162 > Project: Forge > Issue Type: Enhancement > Components: Event Bus, Resources API > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > When project filesystem changes occur, the project can be in a relatively inconsistent state, where facets are not available but are still registered (this is currently detected, but we should probably just fix this the real way by reloading the project metadata) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-220) Forge should listen to filesystem changes on the system and publish events for plugins to observe

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-220: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Forge should listen to filesystem changes on the system and publish events for plugins to observe > -------------------------------------------------------------------------------------------------- > > Key: FORGE-220 > URL: https://issues.jboss.org/browse/FORGE-220 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Resources API, UI - Eclipse > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > {code}Event<ResourceCreated> > Event<ResourceModified> > Event<ResourceDeleted>{code} > etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-273: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > Fix For: 2.x Future > > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-253) Forge should provide development profiles API for datasources and other configs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-253: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Forge should provide development profiles API for datasources and other configs > ------------------------------------------------------------------------------- > > Key: FORGE-253 > URL: https://issues.jboss.org/browse/FORGE-253 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > lincolnthree > It gives you what is in persistence.xml > 11:22 > maxandersen > it wasn't there a jbossworld > 11:22 > lincolnthree > that's been there from the beginning > 11:22 > maxandersen > yes - persistence.xml says datasources > nothing about the actual connection info > 11:23 > lincolnthree > oh right > well > connection info is stored on the server > forge doesn't know that > unless it's in the persistence.xml > 11:23 > maxandersen > lincolnthree: exaactly - but it has to know that eventually. > 11:23 > lincolnthree > as properties > 11:23 > maxandersen > lincolnthree: it wont be > lincolnthree: this is why tools like rails, hibernate tools and others have notion of "profiles" or simply just property overrides for use at design time and for use at runtime -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013