[JBoss JIRA] (FORGE-1392) more command does not always work
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1392:
----------------------------------------
Summary: more command does not always work
Key: FORGE-1392
URL: https://issues.jboss.org/browse/FORGE-1392
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
When I create a project, I can do a {{more}} on the {{pom.xml}}. But then, after creating a few entities, I cannot do a {{more}} on the entity I've created.
{code}
[model]$ more Country.java
/Users/antoniombp/Documents/Code/temp/Country.java: No such file or directory
[model]$ pwd
/Users/antoniombp/Documents/Code/temp/agoncal-application-petstore-ee7/src/main/java/org/agoncal/application/petstore/model
{code}
In this example I am on the {{model}} subdirectory, when I type {{more}} and hit TAB, the completion works for my entity {{Country}}, but then, the directory is not right :
{code}
/Users/antoniombp/Documents/Code/temp/Country.java
{code}
Instead of
{code}
/Users/antoniombp/Documents/Code/temp/agoncal-application-petstore-ee7/src/main/java/org/agoncal/application/petstore/model/Country.java
{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-1391) cd~~ not going back to the project root directory
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1391:
----------------------------------------
Summary: cd~~ not going back to the project root directory
Key: FORGE-1391
URL: https://issues.jboss.org/browse/FORGE-1391
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
No matter in which sub-directory I'm in, {{cd~~}} does not bring me back to the project root directory :
{code}
[model]$ cd ~~
***ERROR*** ~~: No such file or directory
{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-1390) Cannot set the --finalName on a new project
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1390:
----------------------------------------
Summary: Cannot set the --finalName on a new project
Key: FORGE-1390
URL: https://issues.jboss.org/browse/FORGE-1390
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
In Forge 1.x I could set a different {{--finalName}} to a project :
{code}
new-project --named agoncal-application-petstore-ee7 --topLevelPackage org.agoncal.application.petstore --type war --finalName applicationPetstore ;
{code}
I cannot do the same in Forge 2.x because there is no {{--finalName}} attribute to the {{project-new}} command :
{code}
project-new --named agoncal-application-petstore-ee7 --topLevelPackage org.agoncal.application.petstore --type war
{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-1389) rm doesn't remove a none empty directory
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1389:
----------------------------------------
Summary: rm doesn't remove a none empty directory
Key: FORGE-1389
URL: https://issues.jboss.org/browse/FORGE-1389
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
When I try to remove a none empty directory, even with the {{--force}} argument, it doesn't work :
{code}
[temp]$ rm agoncal-application-petstore-ee7
***ERROR*** rm: directory not empty and cannot be removed without '--force' '-f' option.
[temp]$ rm -f agoncal-application-petstore-ee7
***ERROR*** directory not empty
[temp]$ rm --force agoncal-application-petstore-ee7
***ERROR*** directory not empty
{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-1388) set command missing
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1388:
----------------------------------------
Summary: set command missing
Key: FORGE-1388
URL: https://issues.jboss.org/browse/FORGE-1388
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
I'm migrating a Forge 1.x script to 2.x. One of the first command I usually write is :
{code}
set ACCEPT_DEFAULTS true ;
{code}
The {{set}} command hasn't been implemented 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
11 years
[JBoss JIRA] (FORGE-1373) Native Aesh commands do not properly receive/resolve file paths
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1373?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1373:
-------------------------------------
Parent Issue: FORGE-1387 (was: FORGE-1320)
> Native Aesh commands do not properly receive/resolve file paths
> ---------------------------------------------------------------
>
> Key: FORGE-1373
> URL: https://issues.jboss.org/browse/FORGE-1373
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta3
> Reporter: Lincoln Baxter III
> Fix For: 2.0.0.Final
>
>
> {code}
> [Desktop]$ cd ~
> [lb3]$ cd projects/
> [projects]$ less
> .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/
> jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/
> [projects]$ ls
> .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/
> jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/
> [projects]$ less lincoln_javascript_code_style.xml
> /Users/lb3/Desktop/lincoln_javascript_code_style.xml: No such file or directory
> {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-1333) Forge "man" pages are missing for most UI Commands
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1333:
-------------------------------------
Parent Issue: FORGE-1387 (was: FORGE-1320)
> Forge "man" pages are missing for most UI 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