[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1432:
----------------------------------------
Summary: 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
Fix For: 2.x Future
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-1425) Shell issues on Windows
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1425?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1425.
----------------------------------
Assignee: Ståle Pedersen
Fix Version/s: 2.0.0.Final
Resolution: Done
All the issues were fixed in Aesh
> Shell issues on Windows
> -----------------------
>
> Key: FORGE-1425
> URL: https://issues.jboss.org/browse/FORGE-1425
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 2.0.0.Final
> Environment: Windows OS
> Reporter: Ivan St. Ivanov
> Assignee: Ståle Pedersen
> Priority: Blocker
> Fix For: 2.0.0.Final
>
>
> When running Forge on Windows 7, I experienced the following issues:
> - The history doesn't work. That is, when you press up and down arrows instead of the previous commands, you get this: αH
> - Backspace doesn't work. When I press it, the cursor just comes back to the previous position without deleting the character there. If I just write something there, the old symbol is overwritten by the new one, but at the end after pressing enter it looks like you never entered anything after pressing backspace. For example:
> 1) I write new-project --namek
> 2) I notice the typo and press backspace
> 3) k doesn't get deleted, but I overwrite it with d
> 4) Then I complete my command to look like this: new-project --named test
> 5) Forge's output is: Project name must be specified.
> - As you know on Windows the full path to a file or directory is <drive-letter>:\<dir1>\<dir2>
> 1) If I try to do cd c:\temp\forge, Forge blows with exception:
> org.jboss.forge.addon.resource.ResourceException: [FileResourceImpl] can have no
> children
> at org.jboss.forge.addon.resource.AbstractFileResource.getChild(Abstract
> FileResource.java:78)
> at org.jboss.forge.addon.shell.util.PathspecParser.resolve(PathspecParse
> r.java:232)
> at org.jboss.forge.addon.shell.commands.CdCommand.execute(CdCommand.java
> :71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 2) Somehow I noticed that I may use the paths without the drive letter, e.g. just \<dir1>\<dir2>. It is legal to do it in Windows, but thus you can't change to a directory located on a different drive. For example cd \temp\forge will change to c:\temp\forge if you are currently in c:. So I tried cd \temp\forge, but the result was the same exception.
> 3) If I am in the root directory (c:\) and I run cd temp\forge, I don't get exception, but ***ERROR*** tempforge\: No such file or directory. The interesting thing is that I ran that command by pressing tab, i.e. counting on the command completion of the shell, which obviously works fine.
> I made the cd command work by just running cd /temp/forge (notice the forward slashes)
--
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-1312) UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1312?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1312.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Final
(was: 2.x Future)
Resolution: Done
This looks fixed.
> UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed
> ---------------------------------------------------------------------------------------------------
>
> Key: FORGE-1312
> URL: https://issues.jboss.org/browse/FORGE-1312
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha14
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Fix For: 2.0.0.Final
>
>
> Related to FORGE-1131, in the Scaffold setup wizard, I have:
> {noformat}
> @Override
> public Result execute(UIContext context) throws Exception
> {
> ScaffoldProvider selectedProvider = provider.getValue();
> selectedProvider.setup(getSelectedProject(context), createSetupContext());
> return Results.success("Scaffold was setup successfully.");
> }
> {noformat}
> This is expected to be executed only after all other setup wizards and commands have been executed. For example, if the Faces scaffold provider is being setup, then any or all of CDI, EJB, Servlet, Faces and JPA setup wizards must be executed before {{ScaffoldSetupWizard.execute()}} is invoked. This is not the case currently, resulting in {{ScaffoldSetupWizard.execute()}} being invoked first.
--
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-1312) UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1312?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1312:
-------------------------------------------
Is this still a problem? Should be fixed now, right?
> UICommand.execute is executed out of sequence when a list of commands or wizards are to be executed
> ---------------------------------------------------------------------------------------------------
>
> Key: FORGE-1312
> URL: https://issues.jboss.org/browse/FORGE-1312
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha14
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> Related to FORGE-1131, in the Scaffold setup wizard, I have:
> {noformat}
> @Override
> public Result execute(UIContext context) throws Exception
> {
> ScaffoldProvider selectedProvider = provider.getValue();
> selectedProvider.setup(getSelectedProject(context), createSetupContext());
> return Results.success("Scaffold was setup successfully.");
> }
> {noformat}
> This is expected to be executed only after all other setup wizards and commands have been executed. For example, if the Faces scaffold provider is being setup, then any or all of CDI, EJB, Servlet, Faces and JPA setup wizards must be executed before {{ScaffoldSetupWizard.execute()}} is invoked. This is not the case currently, resulting in {{ScaffoldSetupWizard.execute()}} being invoked first.
--
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