[JBoss JIRA] (FORGE-1333) Should command "man" give information about Forge commands ?
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1333:
-------------------------------------------
Just got this feature working :)
> Should command "man" give information about Forge commands ?
> ------------------------------------------------------------
>
> Key: FORGE-1333
> URL: https://issues.jboss.org/browse/FORGE-1333
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> This is more a question because I don't know what {{man}} is suppose to do. This is what I get :
> {code}
> [Test.java]$ man grep
> No manual entry for grep
> [Test.java]$ man echo
> No manual entry for echo
> {code}
> I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual
--
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
[JBoss JIRA] (FORGE-1333) Should command "man" give information about Forge commands ?
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1333:
----------------------------------------
Summary: Should command "man" give information about Forge commands ?
Key: FORGE-1333
URL: https://issues.jboss.org/browse/FORGE-1333
Project: Forge
Issue Type: Sub-task
Reporter: Antonio Goncalves
This is more a question because I don't know what {{man}} is suppose to do. This is what I get :
{code}
[Test.java]$ man grep
No manual entry for grep
[Test.java]$ man echo
No manual entry for echo
{code}
I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual
--
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
[JBoss JIRA] (FORGE-1332) No default nor completion for --typeName
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1332?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1332:
--------------------------------------
Assignee: George Gastaldi
> No default nor completion for --typeName
> ----------------------------------------
>
> Key: FORGE-1332
> URL: https://issues.jboss.org/browse/FORGE-1332
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> When I create a new field on an existing entity I write this :
> {code}
> jpa-new-field --entity org.model.Test --fieldName lastname --typeName String
> ***SUCCESS*** Field lastname created
> {code}
> If I don't write {{String}} the command doesn't give me completion. I would expect that writing the following and hitting TAB would give me some basic datatypes (String, int, float...)
> {code}
> jpa-new-field --entity org.model.Test --fieldName lastname --typeName
> {code}
> And why not having {{String}} as the default type ? This command would create a {{lastname}} of type {{String}} by default :
> {code}
> jpa-new-field --entity org.model.Test --fieldName lastname
> {code}
> Instead I have an error saying that "Type must be specified"
> {code}
> jpa-new-field --entity org.model.Test --fieldName lastname
> Type must be specified
> {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
11 years
[JBoss JIRA] (FORGE-1332) No default nor completion for --typeName
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1332:
----------------------------------------
Summary: No default nor completion for --typeName
Key: FORGE-1332
URL: https://issues.jboss.org/browse/FORGE-1332
Project: Forge
Issue Type: Sub-task
Reporter: Antonio Goncalves
When I create a new field on an existing entity I write this :
{code}
jpa-new-field --entity org.model.Test --fieldName lastname --typeName String
***SUCCESS*** Field lastname created
{code}
If I don't write {{String}} the command doesn't give me completion. I would expect that writing the following and hitting TAB would give me some basic datatypes (String, int, float...)
{code}
jpa-new-field --entity org.model.Test --fieldName lastname --typeName
{code}
And why not having {{String}} as the default type ? This command would create a {{lastname}} of type {{String}} by default :
{code}
jpa-new-field --entity org.model.Test --fieldName lastname
{code}
Instead I have an error saying that "Type must be specified"
{code}
jpa-new-field --entity org.model.Test --fieldName lastname
Type must be specified
{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
11 years
[JBoss JIRA] (FORGE-1330) Rename new-project
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1330?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1330:
-------------------------------------------
Do you really think this is more intuitive than new-project? I have doubts about this change in particular, singly because it is the first command that people need to type, and it would be an un-intuitive change from Forge 1.
I know that this would be inconsistent with the way we are naming things in Forge 2, but I am not sure how to handle this. Let me loop in [~crobson] (our UI expert) and see what she thinks.
> Rename new-project
> ------------------
>
> Key: FORGE-1330
> URL: https://issues.jboss.org/browse/FORGE-1330
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I know this one hurts a bit, but we should really rename :
> {code}
> new-project
> {code}
> To :
> {code}
> project-new
> {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
11 years