May 2013 - forge-issues - Jboss List Archives

[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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > > 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

12 years, 10 months

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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > 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

12 years, 10 months

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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-192: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Make Forge console i18n and L10n compatible > ------------------------------------------- > > Key: FORGE-192 > URL: https://issues.jboss.org/browse/FORGE-192 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - Shell > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha5 > > > Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language. > Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project". -- 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

12 years, 10 months

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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > > 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

12 years, 10 months

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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > > 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

12 years, 10 months

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.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.0.0.Alpha5 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-193) Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-193?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-193: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur > --------------------------------------------------------------------------------- > > Key: FORGE-193 > URL: https://issues.jboss.org/browse/FORGE-193 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, UI - Shell > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > > Should be invalid for same resource scopes > @Alias("whee") > @Alias("whee") > Should be invalid in same command: > @Option(name="named") > @Option(name="named") > And so on... > Or, it should be possible to reference by Fully Qualified Name if this situation does arise (for @Alias.) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-212) Classload dependencies of current project when performing certain operations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-212?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-212: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Classload dependencies of current project when performing certain operations > ----------------------------------------------------------------------------- > > Key: FORGE-212 > URL: https://issues.jboss.org/browse/FORGE-212 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration, Parsers / File Manipulation, Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: wiktorowski maximilien > Priority: Minor > Fix For: 2.0.0.Alpha5 > > > "Generating crud views for entities located into an external jar is a use case i'd like to see implemented in forge. > In my case i have a model.jar containing my entities and an admin.war generated with seam forge. I'd like to use from-entity to generate scaffolding views in admin.war for the entities located in model.jar" > This means that Forge will need to classload dependencies of the target project in order to perform reflection-based generation. This may also require a reflection-based meta-model such as what was done with Errai/GWT. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-238) Log forge commands run against a project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-238?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-238: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Log forge commands run against a project > ---------------------------------------- > > Key: FORGE-238 > URL: https://issues.jboss.org/browse/FORGE-238 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Brian Leathem > Fix For: 2.0.0.Alpha5 > > > ou should have forge create a log file in a project, of all the forge commands you ran in that project. > maybe even script style, so you can play it back. -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2013