[JBoss JIRA] (FORGE-1495) Group or order related command parameters across wizard steps for the Shell UI
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1495?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1495:
-----------------------------------
Description:
Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so:
{noformat}
[helloworld]$ scaffold-setup
--facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion
--configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName
{noformat}
It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both.
was:
Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so:
{{noformat}}
[helloworld]$ scaffold-setup
--facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion
--configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName
{{noformat}}
It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both.
> Group or order related command parameters across wizard steps for the Shell UI
> ------------------------------------------------------------------------------
>
> Key: FORGE-1495
> URL: https://issues.jboss.org/browse/FORGE-1495
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Vineet Reynolds
> Priority: Minor
>
> Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so:
> {noformat}
> [helloworld]$ scaffold-setup
> --facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion
> --configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName
> {noformat}
> It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both.
--
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, 3 months
[JBoss JIRA] (FORGE-1495) Group or order related command parameters across wizards for the Shell UI
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1495:
--------------------------------------
Summary: Group or order related command parameters across wizards for the Shell UI
Key: FORGE-1495
URL: https://issues.jboss.org/browse/FORGE-1495
Project: Forge
Issue Type: Feature Request
Components: UI - Shell
Affects Versions: 2.0.0.CR1
Reporter: Vineet Reynolds
Priority: Minor
Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so:
{{noformat}}
[helloworld]$ scaffold-setup
--facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion
--configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName
{{noformat}}
It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both.
--
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, 3 months
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1432:
-------------------------------------------
Ah, that's because in the current implementation, ';' is actually not required and probably will cause all kinds of Havoc :) I'm working with this today to try to bring back FSH. Hang tight.
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Final
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {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, 3 months
[JBoss JIRA] (FORGE-1169) Port the CDI list-* commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1169?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1169:
-----------------------------------
Description:
Commands in F1:
* beans list-interceptors
* beans list-decorators
* beans list-alternatives
was:
Commands in F1:
* beans setup
* beans list-interceptors
* beans list-decorators
* beans list-alternatives
* beans new-conversation
* beans new-bean
* beans new-qualifier
* beans new-stereotype
* beans new-scope
> Port the CDI list-* commands
> ----------------------------
>
> Key: FORGE-1169
> URL: https://issues.jboss.org/browse/FORGE-1169
> Project: Forge
> Issue Type: Sub-task
> Components: Builtin Plugins
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Fix For: 2.0.0.Final
>
>
> Commands in F1:
> * beans list-interceptors
> * beans list-decorators
> * beans list-alternatives
--
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, 3 months