February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1554) Autocomplete should populate required options without requiring users to key in the option names

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1554?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1554: ----------------------------------- Description: When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named}}. It makes me productive (personal opinion), by not requiring me to key in the option names of commands that are mandatory. Note that this issue is limited in scope to ensuring that mandatory parameter names are completed on TAB. was: When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named}}. It makes me productive (personal opinion), by not requiring me to key in the option names of commands that are mandatory. > Autocomplete should populate required options without requiring users to key in the option names > ------------------------------------------------------------------------------------------------ > > Key: FORGE-1554 > URL: https://issues.jboss.org/browse/FORGE-1554 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. > This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named}}. It makes me productive (personal opinion), by not requiring me to key in the option names of commands that are mandatory. > Note that this issue is limited in scope to ensuring that mandatory parameter names are completed on TAB. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1555) Autocomplete should display options without requiring a user to type in a double hyphen --

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1555: -------------------------------------- Summary: Autocomplete should display options without requiring a user to type in a double hyphen -- Key: FORGE-1555 URL: https://issues.jboss.org/browse/FORGE-1555 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Final Reporter: Vineet Reynolds Fix For: 2.x Future When I key in {noformat} [Order.java]$ jpa-new-field --named description <TAB> {noformat}, I do not get to see the options available for the command, until I key in a double-hyphen, like so: {noformat} [Order.java]$ jpa-new-field --named description -- --targetEntity --type --length --lob {noformat} I think a tying a TAB after a space should display the options for a command. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1554) Autocomplete should populate required options without requiring users to key in the option names

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1554?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1554: ----------------------------------- Description: When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named}}. It makes me productive (personal opinion), by not requiring me to key in the option names of commands that are mandatory. was: When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named }}. It makes me productive (personal opinion), but not requiring me to key in the option names of commands that are mandatory. > Autocomplete should populate required options without requiring users to key in the option names > ------------------------------------------------------------------------------------------------ > > Key: FORGE-1554 > URL: https://issues.jboss.org/browse/FORGE-1554 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. > This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named}}. It makes me productive (personal opinion), by not requiring me to key in the option names of commands that are mandatory. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1554) Autocomplete should populate required options without requiring users to key in the option names

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1554: -------------------------------------- Summary: Autocomplete should populate required options without requiring users to key in the option names Key: FORGE-1554 URL: https://issues.jboss.org/browse/FORGE-1554 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Final Reporter: Vineet Reynolds Fix For: 2.x Future When I key in {{project-new <TAB>}} I expect to see the shell populate the {{--named}} option, since it is a mandatory option. This was the behavior in Forge 1. {{new-project <TAB>}} will auto-complete to {{new-project --named }}. It makes me productive (personal opinion), but not requiring me to key in the option names of commands that are mandatory. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1553) DefaultShellTest is not fully compatible with Results from a Wizard execution

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1553?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1553. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done Fixed by introducing WizardExecutionListener > DefaultShellTest is not fully compatible with Results from a Wizard execution > ----------------------------------------------------------------------------- > > Key: FORGE-1553 > URL: https://issues.jboss.org/browse/FORGE-1553 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to the invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. > The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1553) DefaultShellTest is not fully compatible with Results from a Wizard execution

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1553?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1553: ----------------------------------- Description: When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to the invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution was: When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to multiple invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution > DefaultShellTest is not fully compatible with Results from a Wizard execution > ----------------------------------------------------------------------------- > > Key: FORGE-1553 > URL: https://issues.jboss.org/browse/FORGE-1553 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to the invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. > The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1553) DefaultShellTest is not fully compatible with Results from a Wizard execution

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1553?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1553: ----------------------------------- Description: When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to multiple invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution was:When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. The TestListener should be aware that multiple results are called, however the execution may not have finished yet. > DefaultShellTest is not fully compatible with Results from a Wizard execution > ----------------------------------------------------------------------------- > > Key: FORGE-1553 > URL: https://issues.jboss.org/browse/FORGE-1553 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. This leads to multiple invocation of {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.postCommandExecuted(UICommand, UIExecutionContext, Result)}} several times. > The {{org.jboss.forge.addon.shell.test.impl.DefaultShellTest.TestCommandListener.isExecuted()}} method should be reviewed, since the current impl may return true even if the command has not finished execution -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1553) DefaultShellTest is not fully compatible with Results from a Wizard execution

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1553: -------------------------------------- Summary: DefaultShellTest is not fully compatible with Results from a Wizard execution Key: FORGE-1553 URL: https://issues.jboss.org/browse/FORGE-1553 Project: Forge Issue Type: Bug Components: Test Harness Affects Versions: 2.0.0.Final Reporter: George Gastaldi Fix For: 2.x Future When a wizard is executed, the postCommandExecuted is called for each step in the Wizard. The TestListener should be aware that multiple results are called, however the execution may not have finished yet. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1552) Update homebrew to 1.4.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1552?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1552: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Update homebrew to 1.4.4.Final > ------------------------------ > > Key: FORGE-1552 > URL: https://issues.jboss.org/browse/FORGE-1552 > Project: Forge > Issue Type: Task > Reporter: George Gastaldi > Assignee: George Gastaldi > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1552) Update homebrew to 1.4.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1552?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1552: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/Homebrew/homebrew/pull/26404 > Update homebrew to 1.4.4.Final > ------------------------------ > > Key: FORGE-1552 > URL: https://issues.jboss.org/browse/FORGE-1552 > Project: Forge > Issue Type: Task > Reporter: George Gastaldi > -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014