June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-378. --------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue This will be implemented as an Addon in Forge 2. See FORGE-957 > Add "environments" as a first class construct > --------------------------------------------- > > Key: FORGE-378 > URL: https://issues.jboss.org/browse/FORGE-378 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell, Usability > Reporter: Pete Muir > > For example: > {code} > set environment JBOSS_AS7 --version 7.1.0.Final > {code} > Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. > For example, the persistence plugin could read from this, changing > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS7 > {code} > to > {code} > persistence setup > {code} > Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. > Lot's of other places where this could provide better defaulting, or remove the need to ask questions. > This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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-378) Add "environments" as a first class construct

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] Pete Muir commented on FORGE-378: --------------------------------- I think this is fairly critical to providing a non-schizophrenic user experience for people using plugins. Otherwise we will end up with a similar to forge 1, where each plugin has to ask for a version of everything. > Add "environments" as a first class construct > --------------------------------------------- > > Key: FORGE-378 > URL: https://issues.jboss.org/browse/FORGE-378 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell, Usability > Reporter: Pete Muir > Fix For: 2.x Future > > > For example: > {code} > set environment JBOSS_AS7 --version 7.1.0.Final > {code} > Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. > For example, the persistence plugin could read from this, changing > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS7 > {code} > to > {code} > persistence setup > {code} > Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. > Lot's of other places where this could provide better defaulting, or remove the need to ask questions. > This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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-917) Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-917?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-917: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/324 These changes are introduced outside MetaWidget since the context is not available to determine whether the inspected class is being scaffolded or not. Hence, the decision to avoid scaffolding the class is taken well before inspection. I've taken the decision to omit scaffolding such classes even through they may appear in the search results, since they cannot be searched for, and neither can they be created or updated without using their non-0-arg constructors. Using them otherwise leads to PropertyNotWritableExceptions being thrown due to non-existent setters. Changing the class to add setters is out of question since that would change their immutable property. > Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods > --------------------------------------------------------------------------------------------------- > > Key: FORGE-917 > URL: https://issues.jboss.org/browse/FORGE-917 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.1.Final > > > This is from the TicketMonster model. The create,edit and search views for the {{SectionAllocation}} and {{Ticket}} classes only list the current values of the entities. Creating new entities or editing of existing entities of such classes with user-specified values is not possible. Likewise, searching with a criteria is not possible. > Both these JPA entities have one thing in common, in that they do not have setters for their fields. -- 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-848) Forge should support a @CommandScoped annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-848?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-848: ------------------------------------- Assignee: George Gastaldi > Forge should support a @CommandScoped annotation > ------------------------------------------------ > > Key: FORGE-848 > URL: https://issues.jboss.org/browse/FORGE-848 > Project: Forge > Issue Type: Feature Request > Components: Container, Plugin API > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 1.x Future > > > Forge should support a {{@CommandScoped}} just like the {{@ProjectScoped}} annotation. {{@CommandScoped}} objects would have a shorter lifetime since their lifecycle would be constrained to the execution of a command. This is equivalent to {{@RequestScoped}} instances, so we could renamed {{@CommandScoped}} to {{@RequestScoped}} if appropriate. > Options passed to the Forge plugins could be made available via this scope. Not a binding requirement, since ambiguous dependencies could be encountered when injecting into managed beans. -- 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-848) Forge should support a @CommandScoped annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-848?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-848: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/323 > Forge should support a @CommandScoped annotation > ------------------------------------------------ > > Key: FORGE-848 > URL: https://issues.jboss.org/browse/FORGE-848 > Project: Forge > Issue Type: Feature Request > Components: Container, Plugin API > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > Forge should support a {{@CommandScoped}} just like the {{@ProjectScoped}} annotation. {{@CommandScoped}} objects would have a shorter lifetime since their lifecycle would be constrained to the execution of a command. This is equivalent to {{@RequestScoped}} instances, so we could renamed {{@CommandScoped}} to {{@RequestScoped}} if appropriate. > Options passed to the Forge plugins could be made available via this scope. Not a binding requirement, since ambiguous dependencies could be encountered when injecting into managed beans. -- 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-832) Review modules loaded as system paths in the AbstractModuleLoaderProvider

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-832?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-832: ---------------------------------- Fix Version/s: (was: 1.x Future) > Review modules loaded as system paths in the AbstractModuleLoaderProvider > ------------------------------------------------------------------------- > > Key: FORGE-832 > URL: https://issues.jboss.org/browse/FORGE-832 > Project: Forge > Issue Type: Task > Components: Container > Reporter: James Perkins > > The modules loaded in the {{org.jboss.forge.container.modules.providers.AbstractModuleSpecProvider}} should be reviewed and unneeded modules should be removed. > Currently the following paths appear as if they can be removed: > * log4j > * commons-logging > * cglib -- 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-832) Review modules loaded as system paths in the AbstractModuleLoaderProvider

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-832?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-832: ---------------------------------- Fix Version/s: 2.x Future > Review modules loaded as system paths in the AbstractModuleLoaderProvider > ------------------------------------------------------------------------- > > Key: FORGE-832 > URL: https://issues.jboss.org/browse/FORGE-832 > Project: Forge > Issue Type: Task > Components: Container > Reporter: James Perkins > Fix For: 2.x Future > > > The modules loaded in the {{org.jboss.forge.container.modules.providers.AbstractModuleSpecProvider}} should be reviewed and unneeded modules should be removed. > Currently the following paths appear as if they can be removed: > * log4j > * commons-logging > * cglib -- 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-791) Forge auto complete in windows doesn't display command until after I forge again

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-791?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-791: --------------------------------------- John, I can't reproduce it in Windows 8. Could you test against Forge 1.3.1-SNAPSHOT and check if this behavior still occurs ? Thanks! > Forge auto complete in windows doesn't display command until after I forge again > -------------------------------------------------------------------------------- > > Key: FORGE-791 > URL: https://issues.jboss.org/browse/FORGE-791 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Fix For: 1.x Future > > > If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. > {code} > [ooph] ooph $ sp ^C > spartajs.io > ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] > [ooph] ooph $ > [ooph] ooph $ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > {code} > After hitting forge again it does auto complete properly. -- 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-790) Forge prompts, but then moves forward with an update even if I don't hit enter/Y.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-790?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-790: ---------------------------------- Component/s: UI - Shell Windows > Forge prompts, but then moves forward with an update even if I don't hit enter/Y. > --------------------------------------------------------------------------------- > > Key: FORGE-790 > URL: https://issues.jboss.org/browse/FORGE-790 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Windows > Reporter: John Ament > Fix For: 1.x Future > > > Forge prompts to do an update Y/n when doing forge update. However it skips right past it. > https://gist.github.com/johnament/4977553 > There's also some weird ? being added. -- 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-791) Forge auto complete in windows doesn't display command until after I forge again

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-791?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-791: ---------------------------------- Description: If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. {code} [ooph] ooph $ sp ^C spartajs.io ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] [ooph] ooph $ [ooph] ooph $ forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] {code} After hitting forge again it does auto complete properly. was: If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. [ooph] ooph $ sp ^C spartajs.io ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] [ooph] ooph $ [ooph] ooph $ forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] After hitting forge again it does auto complete properly. > Forge auto complete in windows doesn't display command until after I forge again > -------------------------------------------------------------------------------- > > Key: FORGE-791 > URL: https://issues.jboss.org/browse/FORGE-791 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Fix For: 1.x Future > > > If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. > {code} > [ooph] ooph $ sp ^C > spartajs.io > ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] > [ooph] ooph $ > [ooph] ooph $ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > {code} > After hitting forge again it does auto complete properly. -- 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