[JBoss JIRA] (FORGE-1428) ManProviderTest test are failing with timeout
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1428:
--------------------------------------
Summary: ManProviderTest test are failing with timeout
Key: FORGE-1428
URL: https://issues.jboss.org/browse/FORGE-1428
Project: Forge
Issue Type: Bug
Components: UI - Shell
Reporter: George Gastaldi
Fix For: 2.x Future
{code}
java.util.concurrent.TimeoutException: Timeout expired waiting for command [man exit
] to execute.
STDOUT: [0G[2K[1;34;49m[[22;;39mt[mm[mp[1;34m][22;;39m$[m man exit
[?1049h[0;1mNAME[0;39m
[0;1mexit[0;39m - exit the shell
[0;1mSYNOPSIS[0;39m
[0;1mexit[0;39m
[0;1mDESCRIPTION[0;39m
[0;4mExit[0;39m is a program that triggers shell shutdown. `PreShutdown` events and tasks will be processed prior
to actual shell termination.
[0;1mCOMMANDS[0;39m
none
[0;1mBUGS[0;39m
never
[0;1mAUTHOR[0;39m
The Forge Team
[0;1mRESOURCES[0;39m
forge: <http://forge.jboss.org/>
[7mManual page EXIT(1) line 1 (press h for help or q to quit)[0;39m
STDERR:
BUFFER: [man exit]
at org.jboss.forge.addon.shell.test.impl.DefaultShellTest.throwTimeout(DefaultShellTest.java:433)
at org.jboss.forge.addon.shell.test.impl.DefaultShellTest.execute(DefaultShellTest.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
at org.jboss.forge.addon.shell.test.impl.DefaultShellTest_$$_javassist_17f536d8-cca4-46ba-a359-2d725fd90fb4.execute(DefaultShellTest_$$_javassist_17f536d8-cca4-46ba-a359-2d725fd90fb4.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceLazyLoader.invoke(ExportedInstanceLazyLoader.java:64)
at org.jboss.forge.addon.shell.test.ShellTest_$$_javassist_e4768900-130a-4377-888a-1de397b632f4.execute(ShellTest_$$_javassist_e4768900-130a-4377-888a-1de397b632f4.java)
at org.jboss.forge.addon.shell.aesh.ManProviderTest.testManOutput(ManProviderTest.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
at org.jboss.forge.addon.shell.aesh.ManProviderTest_$$_javassist_844e5631-122b-4492-b3ea-add07e36eff0.testManOutput(ManProviderTest_$$_javassist_844e5631-122b-4492-b3ea-add07e36eff0.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:102)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:75)
at org.jboss.forge.addon.shell.aesh.ManProviderTest_$$_javassist_5eed9c27-f0bb-4f2e-b73e-e4a7036a447e.testManOutput(ManProviderTest_$$_javassist_5eed9c27-f0bb-4f2e-b73e-e4a7036a447e.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:142)
at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
Caused by: java.util.concurrent.TimeoutException: Timeout expired waiting for command [man exit
] to execute.
STDOUT: [0G[2K[1;34;49m[[22;;39mt[mm[mp[1;34m][22;;39m$[m man exit
[?1049h[0;1mNAME[0;39m
[0;1mexit[0;39m - exit the shell
[0;1mSYNOPSIS[0;39m
[0;1mexit[0;39m
[0;1mDESCRIPTION[0;39m
[0;4mExit[0;39m is a program that triggers shell shutdown. `PreShutdown` events and tasks will be processed prior
to actual shell termination.
[0;1mCOMMANDS[0;39m
none
[0;1mBUGS[0;39m
never
[0;1mAUTHOR[0;39m
The Forge Team
[0;1mRESOURCES[0;39m
forge: <http://forge.jboss.org/>
[7mManual page EXIT(1) line 1 (press h for help or q to quit)[0;39m
STDERR:
BUFFER: [man exit]
... 90 more
{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-1428) ManProviderTest tests are failing with timeout
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1428?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1428:
-----------------------------------
Summary: ManProviderTest tests are failing with timeout (was: ManProviderTest test are failing with timeout)
> ManProviderTest tests are failing with timeout
> ----------------------------------------------
>
> Key: FORGE-1428
> URL: https://issues.jboss.org/browse/FORGE-1428
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> {code}
> java.util.concurrent.TimeoutException: Timeout expired waiting for command [man exit
> ] to execute.
> STDOUT: [0G[2K[1;34;49m[[22;;39mt[mm[mp[1;34m][22;;39m$[m man exit
> [?1049h[0;1mNAME[0;39m
> [0;1mexit[0;39m - exit the shell
>
> [0;1mSYNOPSIS[0;39m
> [0;1mexit[0;39m
>
> [0;1mDESCRIPTION[0;39m
> [0;4mExit[0;39m is a program that triggers shell shutdown. `PreShutdown` events and tasks will be processed prior
> to actual shell termination.
>
>
> [0;1mCOMMANDS[0;39m
> none
>
> [0;1mBUGS[0;39m
> never
>
> [0;1mAUTHOR[0;39m
> The Forge Team
>
> [0;1mRESOURCES[0;39m
> forge: <http://forge.jboss.org/>
>
> [7mManual page EXIT(1) line 1 (press h for help or q to quit)[0;39m
> STDERR:
> BUFFER: [man exit]
> at org.jboss.forge.addon.shell.test.impl.DefaultShellTest.throwTimeout(DefaultShellTest.java:433)
> at org.jboss.forge.addon.shell.test.impl.DefaultShellTest.execute(DefaultShellTest.java:95)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
> at org.jboss.forge.addon.shell.test.impl.DefaultShellTest_$$_javassist_17f536d8-cca4-46ba-a359-2d725fd90fb4.execute(DefaultShellTest_$$_javassist_17f536d8-cca4-46ba-a359-2d725fd90fb4.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceLazyLoader.invoke(ExportedInstanceLazyLoader.java:64)
> at org.jboss.forge.addon.shell.test.ShellTest_$$_javassist_e4768900-130a-4377-888a-1de397b632f4.execute(ShellTest_$$_javassist_e4768900-130a-4377-888a-1de397b632f4.java)
> at org.jboss.forge.addon.shell.aesh.ManProviderTest.testManOutput(ManProviderTest.java:66)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
> at org.jboss.forge.addon.shell.aesh.ManProviderTest_$$_javassist_844e5631-122b-4492-b3ea-add07e36eff0.testManOutput(ManProviderTest_$$_javassist_844e5631-122b-4492-b3ea-add07e36eff0.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:102)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:75)
> at org.jboss.forge.addon.shell.aesh.ManProviderTest_$$_javassist_5eed9c27-f0bb-4f2e-b73e-e4a7036a447e.testManOutput(ManProviderTest_$$_javassist_5eed9c27-f0bb-4f2e-b73e-e4a7036a447e.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:142)
> at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
> at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> Caused by: java.util.concurrent.TimeoutException: Timeout expired waiting for command [man exit
> ] to execute.
> STDOUT: [0G[2K[1;34;49m[[22;;39mt[mm[mp[1;34m][22;;39m$[m man exit
> [?1049h[0;1mNAME[0;39m
> [0;1mexit[0;39m - exit the shell
>
> [0;1mSYNOPSIS[0;39m
> [0;1mexit[0;39m
>
> [0;1mDESCRIPTION[0;39m
> [0;4mExit[0;39m is a program that triggers shell shutdown. `PreShutdown` events and tasks will be processed prior
> to actual shell termination.
>
>
> [0;1mCOMMANDS[0;39m
> none
>
> [0;1mBUGS[0;39m
> never
>
> [0;1mAUTHOR[0;39m
> The Forge Team
>
> [0;1mRESOURCES[0;39m
> forge: <http://forge.jboss.org/>
>
> [7mManual page EXIT(1) line 1 (press h for help or q to quit)[0;39m
> STDERR:
> BUFFER: [man exit]
> ... 90 more
> {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-1427) Forge.bat throws error while attempting to install addons
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1427:
--------------------------------------
Summary: Forge.bat throws error while attempting to install addons
Key: FORGE-1427
URL: https://issues.jboss.org/browse/FORGE-1427
Project: Forge
Issue Type: Bug
Components: Init Scripts
Environment: Windows 7
Reporter: George Gastaldi
Priority: Blocker
Fix For: 2.0.0.Final
{code}
C:\Users\George\Documents\GitHub\core\dist\target\forge-distribution-2.0.0-SNAPSHOT\forge-distribution-2.0.0-SNAPSHOT\bin>forge.bat --install org.jboss.forge.addons:core,2.0.0-SNAPSHOT
Unknown option: 2.0.0-SNAPSHOT
java.lang.RuntimeException: Failed to look up versions for [org.jboss.forge.addon:org.jboss.forge.addons:core]
at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.getVersions(MavenAddonDependencyResolver.java:269)
at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveVersions(MavenAddonDependencyResolver.java:147)
at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:205)
at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:152)
at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:92)
Caused by: java.lang.IllegalArgumentException: Bad artifact coordinates org.jboss.forge.addon:org.jboss.forge.addons:core:jar:forge-addon:[,), expected format is <groupId>:<artifactId>[:<extension>[:<classifier>]]:<version>
at org.eclipse.aether.artifact.DefaultArtifact.<init>(DefaultArtifact.java:68)
at org.eclipse.aether.artifact.DefaultArtifact.<init>(DefaultArtifact.java:51)
at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.getVersions(MavenAddonDependencyResolver.java:262)
... 4 more
> Forge version [2.0.0-SNAPSHOT]
{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-1426) Introduce a simpler programming model for UI commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1426?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1426:
--------------------------------------
Assignee: George Gastaldi
> Introduce a simpler programming model for UI commands
> -----------------------------------------------------
>
> Key: FORGE-1426
> URL: https://issues.jboss.org/browse/FORGE-1426
> Project: Forge
> Issue Type: Enhancement
> Components: UI - API
> Affects Versions: 2.0.0.Beta4
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> The UI API already covers a vast majority of use cases, however, implementing UICommand may be too cumbersome for simpler tasks. It would be nice if we could provide a set of annotations (like in Forge 1.x) to speed the development of new UI Commands.
> Initially it would be targeted for single step commands only, but could be extended in the future.
--
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-1426) Introduce a simpler programming model for UI commands
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1426:
--------------------------------------
Summary: Introduce a simpler programming model for UI commands
Key: FORGE-1426
URL: https://issues.jboss.org/browse/FORGE-1426
Project: Forge
Issue Type: Enhancement
Components: UI - API
Affects Versions: 2.0.0.Beta4
Reporter: George Gastaldi
Fix For: 2.x Future
The UI API already covers a vast majority of use cases, however, implementing UICommand may be too cumbersome for simpler tasks. It would be nice if we could provide a set of annotations (like in Forge 1.x) to speed the development of new UI Commands.
Initially it would be targeted for single step commands only, but could be extended in the future.
--
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 updated FORGE-1425:
-----------------------------------
Description:
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)
was:
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)
> 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
> Priority: Blocker
>
> 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-1425) Shell issues on Windows
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1425?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1425:
-----------------------------------
Description:
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)
was:
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:
{code}
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)
{code}
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)
> 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
> Priority: Blocker
>
> 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-1425) Shell issues on Windows
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1425?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1425:
-----------------------------------
Description:
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:
{code}
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)
{code}
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)
was:
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)
> 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
> Priority: Blocker
>
> 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:
> {code}
> 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)
> {code}
> 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-1425) Shell issues on Windows
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGE-1425:
--------------------------------------
Summary: 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
Priority: Blocker
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