December 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1402?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1402: --------------------------------------- Assignee: Vineet Reynolds Reopening and assigning to you vineet. I forgot that this was due to the limitation in Forge 1 > Angularjs plugin does not create supporting beans > -------------------------------------------------- > > Key: FORGE-1402 > URL: https://issues.jboss.org/browse/FORGE-1402 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.4.1.Final > Environment: Mac Maverick with JBDS 7.1 > Reporter: Robb Greathouse > Assignee: Vineet Reynolds > > When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1407) Shell is missing options in wizards where default values allow immediately moving to next step

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1407: ----------------------------------------- Summary: Shell is missing options in wizards where default values allow immediately moving to next step Key: FORGE-1407 URL: https://issues.jboss.org/browse/FORGE-1407 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Lincoln Baxter III Should have a lot more options: {code} [jpa-demo]$ jpa-setup --dataSourceName --dbType --persistenceUnitName {code} The problem is here in ShellWizard.java (in shell addon) {code} private CommandLineParser populate(ShellContext shellContext, String line, final Map<String, InputComponent<?, ?>> inputs) throws Exception { inputs.putAll(getController().getInputs()); CommandLineParser parser = commandLineUtil.generateParser(getController(), shellContext, inputs); CommandLine cmdLine = parser.parse(line, true); Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine, inputs); if (getController().isValid()) { if (getController().canMoveToNextStep()) { // The bug is here. we are immediately moving to the next step and removing all inputs that are not populated. // this really needs to know if we have defaulted to next step or actually moved there willingly // it should not remove old choices until a new choice has been made getController().next().initialize(); inputs.keySet().retainAll(populatedInputs.keySet()); parser = populate(shellContext, line, inputs); } } return parser; } {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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1406) Support customization of Forge generated artifacts in Faces scaffolding

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1406: -------------------------------------- Summary: Support customization of Forge generated artifacts in Faces scaffolding Key: FORGE-1406 URL: https://issues.jboss.org/browse/FORGE-1406 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.0.0.Beta4 Reporter: Vineet Reynolds Currently, the customization of the generated scaffold is limited to the Faces template used for the page. Aspects of the generated scaffold like the managed beans, the CSS files etc. cannot be customized during generation; they have to modified after generation. This feature request is to track the ability to customize any necessary aspects of the generated scaffold. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1402?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1402: ---------------------------------------- Robb, this will have to wait for the plugin to be ported to Forge 2. In Forge 1, I cannot inject and invoke the services of another module (like the Java EE plugin that provides the REST scaffolding) within the AngularJS plugin; doing so would have prevented duplication of code and the need to keep two plugins in sync. The module architecture in Forge 2 does not have this constraint, so you can expect this to not be the case when the Forge 2 addon is released (sometime later this month). > Angularjs plugin does not create supporting beans > -------------------------------------------------- > > Key: FORGE-1402 > URL: https://issues.jboss.org/browse/FORGE-1402 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.4.1.Final > Environment: Mac Maverick with JBDS 7.1 > Reporter: Robb Greathouse > > When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1405) Forge 2.0 Beta4 Does start from command line or in Eclipse

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1405?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1405. ------------------------------------- Resolution: Rejected > Forge 2.0 Beta4 Does start from command line or in Eclipse > ---------------------------------------------------------- > > Key: FORGE-1405 > URL: https://issues.jboss.org/browse/FORGE-1405 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.0.0.Beta4 > Environment: Mac OSX Maverick with JDK 1.7 > Reporter: Robb Greathouse > Priority: Critical > > After adding FORGE_HOME/bin to path using export FORGE_HOME=mypath > export PATH=$PATH:$FORGE_HOME/bin > Then calling forge in the same terminal window Forge starts and gives the line JBoss Forge, version [ 2.0.0.Beta4 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > And promptly hangs and does not give anything else. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1405) Forge 2.0 Beta4 Does start from command line or in Eclipse

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1405?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1405: --------------------------------------- > Forge 2.0 Beta4 Does start from command line or in Eclipse > ---------------------------------------------------------- > > Key: FORGE-1405 > URL: https://issues.jboss.org/browse/FORGE-1405 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.0.0.Beta4 > Environment: Mac OSX Maverick with JDK 1.7 > Reporter: Robb Greathouse > Priority: Critical > > After adding FORGE_HOME/bin to path using export FORGE_HOME=mypath > export PATH=$PATH:$FORGE_HOME/bin > Then calling forge in the same terminal window Forge starts and gives the line JBoss Forge, version [ 2.0.0.Beta4 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > And promptly hangs and does not give anything else. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1405) Forge 2.0 Beta4 Does start from command line or in Eclipse

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1405?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1405. ------------------------------------- Resolution: Duplicate Issue > Forge 2.0 Beta4 Does start from command line or in Eclipse > ---------------------------------------------------------- > > Key: FORGE-1405 > URL: https://issues.jboss.org/browse/FORGE-1405 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.0.0.Beta4 > Environment: Mac OSX Maverick with JDK 1.7 > Reporter: Robb Greathouse > Priority: Critical > > After adding FORGE_HOME/bin to path using export FORGE_HOME=mypath > export PATH=$PATH:$FORGE_HOME/bin > Then calling forge in the same terminal window Forge starts and gives the line JBoss Forge, version [ 2.0.0.Beta4 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > And promptly hangs and does not give anything else. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1405) Forge 2.0 Beta4 Does start from command line or in Eclipse

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1405?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1405: ------------------------------------------- You need to install addons for Forge to do anything. Otherwise you are correct, it will just sit there and do nothing. before running forge, type the following command: {code} forge -i core {code} > Forge 2.0 Beta4 Does start from command line or in Eclipse > ---------------------------------------------------------- > > Key: FORGE-1405 > URL: https://issues.jboss.org/browse/FORGE-1405 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.0.0.Beta4 > Environment: Mac OSX Maverick with JDK 1.7 > Reporter: Robb Greathouse > Priority: Critical > > After adding FORGE_HOME/bin to path using export FORGE_HOME=mypath > export PATH=$PATH:$FORGE_HOME/bin > Then calling forge in the same terminal window Forge starts and gives the line JBoss Forge, version [ 2.0.0.Beta4 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > And promptly hangs and does not give anything else. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1405) Forge 2.0 Beta4 Does start from command line or in Eclipse

by Robb Greathouse (JIRA)

Robb Greathouse created FORGE-1405: -------------------------------------- Summary: Forge 2.0 Beta4 Does start from command line or in Eclipse Key: FORGE-1405 URL: https://issues.jboss.org/browse/FORGE-1405 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 2.0.0.Beta4 Environment: Mac OSX Maverick with JDK 1.7 Reporter: Robb Greathouse Priority: Critical After adding FORGE_HOME/bin to path using export FORGE_HOME=mypath export PATH=$PATH:$FORGE_HOME/bin Then calling forge in the same terminal window Forge starts and gives the line JBoss Forge, version [ 2.0.0.Beta4 ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] And promptly hangs and does not give anything else. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1404) Option names with default values are not displayed when <TAB> is pressed

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1404: -------------------------------------- Summary: Option names with default values are not displayed when <TAB> is pressed Key: FORGE-1404 URL: https://issues.jboss.org/browse/FORGE-1404 Project: Forge Issue Type: Bug Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: George Gastaldi Priority: Critical Fix For: 2.x Future Eg: {{jpa-setup --container <TAB>}} shows a list of containers, however {{jpa-setup <TAB>}} doesn't display the {{container}} option -- 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

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2013