[jira] Created: (GSHELL-163) Upgrade to org.apache.sshd 0.1.0
Upgrade to org.apache.sshd 0.1.0 Key: GSHELL-163 URL: https://issues.apache.org/jira/browse/GSHELL-163 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - SSH Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-163) Upgrade to org.apache.sshd 0.1.0
[ https://issues.apache.org/jira/browse/GSHELL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-163. --- Resolution: Fixed Upgrade to org.apache.sshd 0.1.0 Key: GSHELL-163 URL: https://issues.apache.org/jira/browse/GSHELL-163 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Commands - SSH Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4709) start-server's -j flag does not work
[ https://issues.apache.org/jira/browse/GERONIMO-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-4709: --- Summary: start-server's -j flag does not work (was: start-servers' -j flag does not work) start-server's -j flag does not work Key: GERONIMO-4709 URL: https://issues.apache.org/jira/browse/GERONIMO-4709 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.4 Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 2.1.5, 2.2 Problem is that node.setAttribute(String, String) won't coerce 2nd param of type java.io.File to string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4709) start-servers' -j flag does not work
start-servers' -j flag does not work Key: GERONIMO-4709 URL: https://issues.apache.org/jira/browse/GERONIMO-4709 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 2.1.4 Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 2.1.5, 2.2 Problem is that node.setAttribute(String, String) won't coerce 2nd param of type java.io.File to string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4709) start-server's -j flag does not work
[ https://issues.apache.org/jira/browse/GERONIMO-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-4709. -- Resolution: Fixed start-server's -j flag does not work Key: GERONIMO-4709 URL: https://issues.apache.org/jira/browse/GERONIMO-4709 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.4 Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 2.1.5, 2.2 Problem is that node.setAttribute(String, String) won't coerce 2nd param of type java.io.File to string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4557) geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
[ https://issues.apache.org/jira/browse/GERONIMO-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677271#action_12677271 ] Jason Dillon commented on GERONIMO-4557: This is not a GShell issue... its a Geronimo issue with its GShell command implementations. Moved from GSHELL to GERONIMO. In the future please do not file issues which are related to a Geronimo GShell command impl in the GSHELL JIRA project. geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties. -- Key: GERONIMO-4557 URL: https://issues.apache.org/jira/browse/GERONIMO-4557 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Environment: XP + SUN JDK 1.5 + geronimo-tomcat-2.1.4-snapshot_20090225 Reporter: Shawn Jiang Assignee: Jason Dillon Reproduce steps: 1, Change NamingPort=3099 in var/config-substitutions.properties. 2, Use GShell command geronimo/start-server to start the server. 3, Use Use GShell command geronimo/stop-server -p 3099 to stop the server. Expected result: the server could be shutdown and return to the GShell command line mode. Actually result: The server can't be shutdown, can't return to the GShell command line. Root Cause: You have to use geronimo/start-server -p 3099 to start server if you want use geronimo/stop-server -p 3099 to stop the server. I believe there should not be a -p args for geronimo/start-server command. Instead, geronimo/start-server should read NamingPort=3099 in config.substitutions.properties to avoid the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4557) geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
[ https://issues.apache.org/jira/browse/GERONIMO-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GERONIMO-4557: -- Assignee: (was: Jason Dillon) geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties. -- Key: GERONIMO-4557 URL: https://issues.apache.org/jira/browse/GERONIMO-4557 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Environment: XP + SUN JDK 1.5 + geronimo-tomcat-2.1.4-snapshot_20090225 Reporter: Shawn Jiang Reproduce steps: 1, Change NamingPort=3099 in var/config-substitutions.properties. 2, Use GShell command geronimo/start-server to start the server. 3, Use Use GShell command geronimo/stop-server -p 3099 to stop the server. Expected result: the server could be shutdown and return to the GShell command line mode. Actually result: The server can't be shutdown, can't return to the GShell command line. Root Cause: You have to use geronimo/start-server -p 3099 to start server if you want use geronimo/stop-server -p 3099 to stop the server. I believe there should not be a -p args for geronimo/start-server command. Instead, geronimo/start-server should read NamingPort=3099 in config.substitutions.properties to avoid the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-159) NegativeArraySizeException is thrown when using just the Shell Impementation when running tests.
[ https://issues.apache.org/jira/browse/GSHELL-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673267#action_12673267 ] Jason Dillon commented on GSHELL-159: - This should have been fixed by the gshell-terminal module's jline terminal adapters. NegativeArraySizeException is thrown when using just the Shell Impementation when running tests. Key: GSHELL-159 URL: https://issues.apache.org/jira/browse/GSHELL-159 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Components: Wisdom Affects Versions: 1.0-alpha-2 Reporter: Edell Nolan Assignee: Jason Dillon Attachments: gshell-159.patch If just using the shell implementation when running tests - a real teminal may not be created and as a result the teminalWidth results in a negative value. Example: Is using the servicemix kernel gshell itests [localShell] ERROR org.apache.servicemix.kernel.gshell.core.LocalConsole - Exiti ng shell due to caught exception java.lang.NegativeArraySizeException java.lang.NegativeArraySizeException at java.lang.AbstractStringBuilder.init(AbstractStringBuilder.java:44) at java.lang.StringBuilder.init(StringBuilder.java:81) at org.apache.geronimo.gshell.wisdom.shell.ShellImpl.repeat(ShellImpl.ja va:265) at org.apache.geronimo.gshell.wisdom.shell.ShellImpl.run(ShellImpl.java: 242) at org.apache.servicemix.kernel.gshell.core.ShellWrapper.run(ShellWrappe r.java:81) at org.apache.servicemix.kernel.gshell.core.LocalConsole.run(LocalConsol e.java:125) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-157) Dynamically adding / removing commands does not work well
[ https://issues.apache.org/jira/browse/GSHELL-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671563#action_12671563 ] Jason Dillon commented on GSHELL-157: - Ya, a side effect of leaning on VFS to handle the storage, I notice there is a problem with setting/unsetting/setting aliases too. Dynamically adding / removing commands does not work well - Key: GSHELL-157 URL: https://issues.apache.org/jira/browse/GSHELL-157 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 When resolving commands, the command resolver uses a virtual file system. Unfortunately, the data for virtual file systems is always cached, which means that removing a command will still make it available for resolution. The cache problem is caused by the DelegateFileObject which does not refresh the underlying file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-156) Disable system bell by default
[ https://issues.apache.org/jira/browse/GSHELL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668766#action_12668766 ] Jason Dillon commented on GSHELL-156: - I'm tempted to leave it in there just to annoy windows users, *nix and Mac OSX (which is a *nix system btw) don't disregard the bell, its just easier to configure if its on or off. I suggest you a) switch to a real operating system or b) google how to disable the bell from your cmd.exe (or whatever console app you are using). Disable system bell by default -- Key: GSHELL-156 URL: https://issues.apache.org/jira/browse/GSHELL-156 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Commands - Shell Affects Versions: 1.0-alpha-2 Environment: Windows Reporter: Chris Custine Assignee: Jason Dillon Priority: Minor Attachments: nobell.patch On WIndows, attempting to backspace at the beginning of a line causes the system bell to sound, thereby knocking many a user off their chair. I would recommend disabling this for the sake of Windows users. *nix systems and Mac OSX shells seem to disregard the system bell commands by default so disabling the system bell in the ConsoleReader by default shouldn't affect them adversely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4170) Upgrade Selenium version for Firefox 3
[ https://issues.apache.org/jira/browse/GERONIMO-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reopened GERONIMO-4170: Assignee: Jason Dillon (was: Donald Woods) Upgrade Selenium version for Firefox 3 -- Key: GERONIMO-4170 URL: https://issues.apache.org/jira/browse/GERONIMO-4170 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: testsuite Affects Versions: 2.1.2, 2.2 Reporter: Donald Woods Assignee: Jason Dillon Priority: Minor Fix For: 2.2 The current Selenium 1.0-beta-1 artifacts do not support using Firefox3 (on Linux or MacOSX.) When a snapshot or next beta does support FF3, then we should upgrade. The current 1.0-SNAPSHOT artifacts as of the 20080627 version still does not work with FF3 on Linux. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4170) Upgrade Selenium version for Firefox 3
[ https://issues.apache.org/jira/browse/GERONIMO-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-4170. -- Resolution: Fixed Fix Version/s: (was: 2.1.4) Upgraded to selenium-maven-plugin 1.0-rc-1 which uses selenium 1.0-beta-2 Upgrade Selenium version for Firefox 3 -- Key: GERONIMO-4170 URL: https://issues.apache.org/jira/browse/GERONIMO-4170 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: testsuite Affects Versions: 2.1.2, 2.2 Reporter: Donald Woods Assignee: Jason Dillon Priority: Minor Fix For: 2.2 The current Selenium 1.0-beta-1 artifacts do not support using Firefox3 (on Linux or MacOSX.) When a snapshot or next beta does support FF3, then we should upgrade. The current 1.0-SNAPSHOT artifacts as of the 20080627 version still does not work with FF3 on Linux. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-150) Add support to resolve artifacts with Maven Mercury
Add support to resolve artifacts with Maven Mercury --- Key: GSHELL-150 URL: https://issues.apache.org/jira/browse/GSHELL-150 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Artifact + Mercury Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-151) Repackage org.apache.geronimo.gshell.* - org.apache.gshell.*
Repackage org.apache.geronimo.gshell.* - org.apache.gshell.* - Key: GSHELL-151 URL: https://issues.apache.org/jira/browse/GSHELL-151 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Build Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-beta-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-152) Add gshell-maven-plugin to allow command execution via mvn
Add gshell-maven-plugin to allow command execution via mvn -- Key: GSHELL-152 URL: https://issues.apache.org/jira/browse/GSHELL-152 Project: GShell Issue Type: New Feature Security Level: public (Regular issues) Components: Build Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-153) Configure the maven-license-plugin
Configure the maven-license-plugin -- Key: GSHELL-153 URL: https://issues.apache.org/jira/browse/GSHELL-153 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Build Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-152) Add gshell-maven-plugin to allow command execution via mvn
[ https://issues.apache.org/jira/browse/GSHELL-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-152: Component/s: (was: Build) Maven Plugin Add gshell-maven-plugin to allow command execution via mvn -- Key: GSHELL-152 URL: https://issues.apache.org/jira/browse/GSHELL-152 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Maven Plugin Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-153) Configure the maven-license-plugin
[
https://issues.apache.org/jira/browse/GSHELL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-153.
---
Resolution: Fixed
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
This is done in Genesis 2.0-SNAPSHOT, use {{mvn -Plicense-check}} to run.
Configure the maven-license-plugin
--
Key: GSHELL-153
URL: https://issues.apache.org/jira/browse/GSHELL-153
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Build
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-149) Get the default value for 'gshell.prompt' from Application/Branding
[ https://issues.apache.org/jira/browse/GSHELL-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-149. --- Resolution: Fixed Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Get the default value for 'gshell.prompt' from Application/Branding --- Key: GSHELL-149 URL: https://issues.apache.org/jira/browse/GSHELL-149 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Application, Wisdom Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-122) Update to Apache BSF 3.0
Update to Apache BSF 3.0 Key: GSHELL-122 URL: https://issues.apache.org/jira/browse/GSHELL-122 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - BSF Reporter: Jason Dillon Assignee: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 May require Java 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-123) Add commands to install/manage scripting language engines
Add commands to install/manage scripting language engines - Key: GSHELL-123 URL: https://issues.apache.org/jira/browse/GSHELL-123 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - BSF Reporter: Jason Dillon Assignee: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-124) Merge Branding into Application
Merge Branding into Application --- Key: GSHELL-124 URL: https://issues.apache.org/jira/browse/GSHELL-124 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Application Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-125) Hook up gshell-artifact TransferListener to Ivy
Hook up gshell-artifact TransferListener to Ivy --- Key: GSHELL-125 URL: https://issues.apache.org/jira/browse/GSHELL-125 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Artifact + Ivy Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-126) Expose more repository configuration of policies and such
Expose more repository configuration of policies and such - Key: GSHELL-126 URL: https://issues.apache.org/jira/browse/GSHELL-126 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Artifact + Maven Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-128) Add flag to capture output to a log file
Add flag to capture output to a log file Key: GSHELL-128 URL: https://issues.apache.org/jira/browse/GSHELL-128 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: CLI Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-127) Support loading optional properties file for custom persistent configuration customization
Support loading optional properties file for custom persistent configuration customization -- Key: GSHELL-127 URL: https://issues.apache.org/jira/browse/GSHELL-127 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Bootstrap Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-131) Fix i18n usage for CLP
Fix i18n usage for CLP -- Key: GSHELL-131 URL: https://issues.apache.org/jira/browse/GSHELL-131 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - CLP Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-alpha-3 Actually, the CLP might need a larger re-write to fix some of its deficiencies and add more features, like to configure default values, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-132) Sort the command list for 'help' output
Sort the command list for 'help' output --- Key: GSHELL-132 URL: https://issues.apache.org/jira/browse/GSHELL-132 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - Builtin Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-133) (history) Add range, clear and recall support
(history) Add range, clear and recall support - Key: GSHELL-133 URL: https://issues.apache.org/jira/browse/GSHELL-133 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - Builtin Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-135) (resolve) Use the generic gshell-artifact ArtifactResolver interface
(resolve) Use the generic gshell-artifact ArtifactResolver interface Key: GSHELL-135 URL: https://issues.apache.org/jira/browse/GSHELL-135 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - Repository Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-134) (about) Add more options to query more application details
(about) Add more options to query more application details -- Key: GSHELL-134 URL: https://issues.apache.org/jira/browse/GSHELL-134 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - Builtin Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-132) (help) Sort the command list
[ https://issues.apache.org/jira/browse/GSHELL-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-132: Summary: (help) Sort the command list (was: Sort the command list for 'help' output) (help) Sort the command list Key: GSHELL-132 URL: https://issues.apache.org/jira/browse/GSHELL-132 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Commands - Builtin Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-136) (ssh) Parse username@hostname
(ssh) Parse username@hostname - Key: GSHELL-136 URL: https://issues.apache.org/jira/browse/GSHELL-136 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Commands - SSH Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-137) Expose jline binding configuration
Expose jline binding configuration -- Key: GSHELL-137 URL: https://issues.apache.org/jira/browse/GSHELL-137 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Console Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-129) Add --file file option to run: source file
Add --file file option to run: source file -- Key: GSHELL-129 URL: https://issues.apache.org/jira/browse/GSHELL-129 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: CLI Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-130) Add option to allow the application.xml location to be configured
Add option to allow the application.xml location to be configured - Key: GSHELL-130 URL: https://issues.apache.org/jira/browse/GSHELL-130 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: CLI Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-139) Support hijacking of System.in
Support hijacking of System.in -- Key: GSHELL-139 URL: https://issues.apache.org/jira/browse/GSHELL-139 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - IO Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-138) Redesign IO, it has many problems/hacks
Redesign IO, it has many problems/hacks --- Key: GSHELL-138 URL: https://issues.apache.org/jira/browse/GSHELL-138 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - IO Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-141) Support optional validation of spring configuration files
Support optional validation of spring configuration files - Key: GSHELL-141 URL: https://issues.apache.org/jira/browse/GSHELL-141 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Spring Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-142) Generate+cache fastinfoset documents dynamically to speed up plugin loading (second time)
Generate+cache fastinfoset documents dynamically to speed up plugin loading (second time) - Key: GSHELL-142 URL: https://issues.apache.org/jira/browse/GSHELL-142 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Spring Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-144) Implement ApplictaionSecurityManager properly
Implement ApplictaionSecurityManager properly - Key: GSHELL-144 URL: https://issues.apache.org/jira/browse/GSHELL-144 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Wisdom Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-143) Handle space encoding for file completer operations
Handle space encoding for file completer operations --- Key: GSHELL-143 URL: https://issues.apache.org/jira/browse/GSHELL-143 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - VFS Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-146) Use of VFS for alias details causes problems to due VFS file cache
Use of VFS for alias details causes problems to due VFS file cache -- Key: GSHELL-146 URL: https://issues.apache.org/jira/browse/GSHELL-146 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 1.0-alpha-3 Redefined aliases will not have new values picked up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-145) Handle removing meta:/plugins/name when plugin is removed
Handle removing meta:/plugins/name when plugin is removed --- Key: GSHELL-145 URL: https://issues.apache.org/jira/browse/GSHELL-145 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Wisdom Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-149) Get the default value for 'gshell.prompt' from Application/Branding
Get the default value for 'gshell.prompt' from Application/Branding --- Key: GSHELL-149 URL: https://issues.apache.org/jira/browse/GSHELL-149 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Application, Wisdom Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-147) Create ANSI Throwable stack render utility
Create ANSI Throwable stack render utility -- Key: GSHELL-147 URL: https://issues.apache.org/jira/browse/GSHELL-147 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - ANSI, Wisdom Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 Currently this is handled by the ConsoleErrorHandleImpl, should be genericly available in gshell-ansi. Also, the current impl does not properly render nested details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-148) Implement annotation-based toString() bits
Implement annotation-based toString() bits -- Key: GSHELL-148 URL: https://issues.apache.org/jira/browse/GSHELL-148 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Support - Yarn Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-127) Support loading optional properties file for custom persistent configuration customization
[
https://issues.apache.org/jira/browse/GSHELL-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-127:
Priority: Critical (was: Major)
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Looks like this is going to be needed for integration into Geronimo, as well as
some other configurable bits, like to change ${gshell.home}/lib to
${gshell.home}/lib/gshell, etc.
Support loading optional properties file for custom persistent configuration
customization
--
Key: GSHELL-127
URL: https://issues.apache.org/jira/browse/GSHELL-127
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Bootstrap
Reporter: Jason Dillon
Assignee: Jason Dillon
Priority: Critical
Fix For: 1.0-alpha-2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-81) Depdendency on sun.* packages
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652369#action_12652369
]
Jason Dillon commented on GSHELL-81:
Why was this reopened?
Depdendency on sun.* packages
-
Key: GSHELL-81
URL: https://issues.apache.org/jira/browse/GSHELL-81
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Support - Marshal
Reporter: Guillaume Nodet
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
It seems that GShell is currently unable to run without the sun.* packages in
the classloader.
The reason is that it uses xstream advanced mode which make use of these
packages.
If these packages are not on the classpath, xstream will default to the pure
java reflection provider which will cause exceptions like the following:
{noformat}
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot
construct org.apache.geronimo.gshell.layout.model.CommandNode as it does not
have a no-args constructor
Debugging information
message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
cause-exception :
com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
class : org.apache.geronimo.gshell.layout.model.Layout
required-type : org.apache.geronimo.gshell.layout.model.CommandNode
path: /layout/nodes/command
---
{noformat}
I'm not sure if this is a good idea or if we should support that pure java
mode...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-81) Depdendency on sun.* packages
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-81.
--
Resolution: Won't Fix
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
XStream is currently not used directly, so this is not something that needs to
be fixed.
Depdendency on sun.* packages
-
Key: GSHELL-81
URL: https://issues.apache.org/jira/browse/GSHELL-81
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Support - Marshal
Reporter: Guillaume Nodet
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
It seems that GShell is currently unable to run without the sun.* packages in
the classloader.
The reason is that it uses xstream advanced mode which make use of these
packages.
If these packages are not on the classpath, xstream will default to the pure
java reflection provider which will cause exceptions like the following:
{noformat}
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot
construct org.apache.geronimo.gshell.layout.model.CommandNode as it does not
have a no-args constructor
Debugging information
message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
cause-exception :
com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
class : org.apache.geronimo.gshell.layout.model.Layout
required-type : org.apache.geronimo.gshell.layout.model.CommandNode
path: /layout/nodes/command
---
{noformat}
I'm not sure if this is a good idea or if we should support that pure java
mode...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-82) Bring the testsuite back
[ https://issues.apache.org/jira/browse/GSHELL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-82: --- Fix Version/s: (was: 1.0-alpha-2) 1.0-alpha-3 Defer until next release. Bring the testsuite back Key: GSHELL-82 URL: https://issues.apache.org/jira/browse/GSHELL-82 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Build Reporter: Jason Dillon Assignee: Jason Dillon Priority: Blocker Fix For: 1.0-alpha-3 Need to bring the testsuite back so that we can create integration tests for commands. Actually need to see if we can use SHITTY to allow command modules to create localized integration tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-47) Add flag (and support) to capture the output of a gsh run to a log-file configured on the cli
[
https://issues.apache.org/jira/browse/GSHELL-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-47:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
Add flag (and support) to capture the output of a gsh run to a log-file
configured on the cli
-
Key: GSHELL-47
URL: https://issues.apache.org/jira/browse/GSHELL-47
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: CLI
Affects Versions: 1.0-alpha-1
Reporter: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-3
Should be able to specify something like:
{noformat}
./bin/gsh --logfile output.log
{noformat}
And have all of the output captured to a file named {{output.log}}, or
whatever was given to the {{--logfile}} option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-69) gsh -c should soak up all remaining arguments and build a command-line
[
https://issues.apache.org/jira/browse/GSHELL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-69:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
gsh -c should soak up all remaining arguments and build a command-line
--
Key: GSHELL-69
URL: https://issues.apache.org/jira/browse/GSHELL-69
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: CLI
Affects Versions: 1.0-alpha-1
Reporter: Jason Dillon
Assignee: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-3
Right now {{-c}} takes a list of arguments to run non-interactively. It
should instead take all remaining arguments for execution non-interactively.
This means that {{-c}} can contain easily quoted arguments if needed and
should simplify usage of gsh for non-interactive usage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-68) CLP should allow -vvv to be treated like -v -v -v
[ https://issues.apache.org/jira/browse/GSHELL-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-68: --- Fix Version/s: (was: 1.0-alpha-2) 1.0-alpha-3 Defer until next release. CLP should allow -vvv to be treated like -v -v -v - Key: GSHELL-68 URL: https://issues.apache.org/jira/browse/GSHELL-68 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Support - CLP Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-67) Allow the clp to generate help text with ANSI colors
[
https://issues.apache.org/jira/browse/GSHELL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-67:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Defer until next release.
Allow the clp to generate help text with ANSI colors
Key: GSHELL-67
URL: https://issues.apache.org/jira/browse/GSHELL-67
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Support - CLP
Reporter: Jason Dillon
Priority: Trivial
Fix For: 1.0-alpha-3
Generated {{--help}} text should probably use ANSI to highlight things, and
allow embedded {{|@xxx yyy|}} syntax for implementors to provide specific
coloring.
This basically means using the ANSI renderer in the CLP printer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-43) Add role-based layout selection
[ https://issues.apache.org/jira/browse/GSHELL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-43: --- Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Add role-based layout selection --- Key: GSHELL-43 URL: https://issues.apache.org/jira/browse/GSHELL-43 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-2 Add support to select a different layout based on the user who is logged in. Some users might need only basic commands while others might need a full range (of admin or potentially harmful commands). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-23) Command pipe-lines
[
https://issues.apache.org/jira/browse/GSHELL-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-23.
--
Resolution: Fixed
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Assignee: Jason Dillon (was: Erik B. Craig)
Basic support is in for this.
Command pipe-lines
--
Key: GSHELL-23
URL: https://issues.apache.org/jira/browse/GSHELL-23
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Parser
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
Add support for piping the output of one command into another, as in:
{noformat}
echo hi | cat /tmp/foo
{noformat}
This should write hi to the /tmp/foo file.
Follow zsh style, allowing | to concat both stdout+stderr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-3) Hook up backtick and execute assign bits... foo=`echo bar`
[ https://issues.apache.org/jira/browse/GSHELL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-3: -- Component/s: Parser Hook up backtick and execute assign bits... foo=`echo bar` -- Key: GSHELL-3 URL: https://issues.apache.org/jira/browse/GSHELL-3 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Parser Affects Versions: 0.0.1 Reporter: Jason Dillon Priority: Critical Fix For: 1.0-alpha-3 Hook up backtick and execute assign bits... foo=`echo bar` Dunno if this captures the output of 'echo bar' or the return of the command Might need to have both? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-24) Support background commands
[
https://issues.apache.org/jira/browse/GSHELL-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-24:
---
Component/s: Parser
Support background commands
---
Key: GSHELL-24
URL: https://issues.apache.org/jira/browse/GSHELL-24
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Parser
Reporter: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-3
Should be able to background a command using the {{}} token.
Also need to be able to {{bg}}, {{fg}} and enumerate {{jobs}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-40) Add annotation-based preferences injection support
[ https://issues.apache.org/jira/browse/GSHELL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-40: --- Component/s: Support Add annotation-based preferences injection support -- Key: GSHELL-40 URL: https://issues.apache.org/jira/browse/GSHELL-40 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 Add a simple annotation-based API to allow the preferences API to be used by commands (similar to how the CLP stuff makes it simple to handle command-line options and arguments). A skeleton project is setup here for the prefs stuff: * https://svn.apache.org/repos/asf/geronimo/gshell/trunk/gshell-support/gshell-prefs/ Probably need to have an annotation for types to denote the prefs node, and then have a preferences annotation with optional node definition for overrides. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-18) New command: exec
[ https://issues.apache.org/jira/browse/GSHELL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-18. -- Resolution: Fixed exec seems to be working fine. New command: exec - Key: GSHELL-18 URL: https://issues.apache.org/jira/browse/GSHELL-18 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Commands - Builtins Reporter: Jason Dillon Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-18) New command: exec
[ https://issues.apache.org/jira/browse/GSHELL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-18: --- Component/s: (was: Commands) Commands - Builtins Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 New command: exec - Key: GSHELL-18 URL: https://issues.apache.org/jira/browse/GSHELL-18 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Commands - Builtins Reporter: Jason Dillon Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-16) New command: ssh
[
https://issues.apache.org/jira/browse/GSHELL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-16.
--
Resolution: Fixed
Going with the ssh client library from the new sshd library.
New command: ssh
Key: GSHELL-16
URL: https://issues.apache.org/jira/browse/GSHELL-16
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Commands
Affects Versions: 1.0-alpha-2
Reporter: Jason Dillon
Assignee: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-2
Attachments: GSHELL-16.patch
Create a {{ssh}} command that provides similar functionality to the unix
shell equivalent {{ssh}} (and {{scp}}) commands inside of GShell.
Can wrap the Jsch API to make a ssh command.
Basically, this command will allow a user inside of GShell to make a
connection to a normal {{sshd}} server, run some commands and/or transfer
some files and even setup port forwarding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-81) Depdendency on sun.* packages
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-81:
---
Component/s: Support - Marshal
Depdendency on sun.* packages
-
Key: GSHELL-81
URL: https://issues.apache.org/jira/browse/GSHELL-81
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Support - Marshal
Reporter: Guillaume Nodet
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
It seems that GShell is currently unable to run without the sun.* packages in
the classloader.
The reason is that it uses xstream advanced mode which make use of these
packages.
If these packages are not on the classpath, xstream will default to the pure
java reflection provider which will cause exceptions like the following:
{noformat}
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot
construct org.apache.geronimo.gshell.layout.model.CommandNode as it does not
have a no-args constructor
Debugging information
message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
cause-exception :
com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
class : org.apache.geronimo.gshell.layout.model.Layout
required-type : org.apache.geronimo.gshell.layout.model.CommandNode
path: /layout/nodes/command
---
{noformat}
I'm not sure if this is a good idea or if we should support that pure java
mode...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-1) Add ${...} parsing to the CommandLineParser; remove VariableExpressionParser
[
https://issues.apache.org/jira/browse/GSHELL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-1:
--
Component/s: Support - Interpolation
Parser
Add ${...} parsing to the CommandLineParser; remove VariableExpressionParser
Key: GSHELL-1
URL: https://issues.apache.org/jira/browse/GSHELL-1
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Parser, Support - Interpolation
Affects Versions: 0.0.1
Reporter: Jason Dillon
Priority: Critical
Fix For: 1.0-alpha-3
Currently variable references are post-parsed because that was easier to get
implemented. The CL parser should be able to handle all parsing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-52) Expose real SSL configuration bits
[
https://issues.apache.org/jira/browse/GSHELL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-52.
--
Resolution: Won't Fix
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Ssl stuff has been replaced by the new ssh support.
Expose real SSL configuration bits
--
Key: GSHELL-52
URL: https://issues.apache.org/jira/browse/GSHELL-52
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Affects Versions: 1.0-alpha-1
Reporter: Jason Dillon
Fix For: 1.0-alpha-2
Right now for SSL, the {{BogusSSLContextFactory}} is used. This works, but
isn't very nice for folks that want to use their own certs and/or configure
client-auth and such. So we should create a new factory which is more
configurable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-25) Sub-shell syntax support
[
https://issues.apache.org/jira/browse/GSHELL-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-25:
---
Component/s: Parser
Commands - Builtins
Sub-shell syntax support
Key: GSHELL-25
URL: https://issues.apache.org/jira/browse/GSHELL-25
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Commands - Builtins, Parser
Reporter: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-3
Support constructs like:
{noformat}
set a=b ; (set a=c; echo $a); echo $a
{noformat}
This should create 2 shells. and result in:
{noformat}
c
b
{noformat}
Executes as follows:
* set a=b
** set a=c
** echo $a
* echo $a
Intenally the sub-shell is delegated to the builtin subshell command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-17) New command: subshell
[ https://issues.apache.org/jira/browse/GSHELL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-17: --- Component/s: (was: Commands) Commands - Builtins New command: subshell - Key: GSHELL-17 URL: https://issues.apache.org/jira/browse/GSHELL-17 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Commands - Builtins Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-38) Add rfile:// remote-file support to allow rsh clients to access files from the local machine
[ https://issues.apache.org/jira/browse/GSHELL-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-38. -- Resolution: Won't Fix Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Dropped custom remote muck in favor of using ssh. Add rfile:// remote-file support to allow rsh clients to access files from the local machine Key: GSHELL-38 URL: https://issues.apache.org/jira/browse/GSHELL-38 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Remote Shell, Whisper Affects Versions: 1.0-alpha-1 Reporter: Jason Dillon Fix For: 1.0-alpha-2 Need to provide a _simple_ way for files on a local machine (one where an rsh originates from) on the remote machine (where the rshd is accepting connections). Probably want to implement a URLConnection handler, perhaps using VFS too, so provide even richer remote file access to commands via URLs. Skeleton classes for the URL muck and Whisper protocol messages are here: * https://svn.apache.org/repos/asf/geronimo/gshell/trunk/gshell-whisper/src/main/java/org/apache/geronimo/gshell/whisper/rfile -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-120) Consider using JSecurity
[ https://issues.apache.org/jira/browse/GSHELL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-120. --- Resolution: Fixed Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 JSecurity is used for sshd auth. Consider using JSecurity Key: GSHELL-120 URL: https://issues.apache.org/jira/browse/GSHELL-120 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-2 http://www.jsecurity.org/docs/quickstart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-51) Generalize the transport access on per-thread bases
[ https://issues.apache.org/jira/browse/GSHELL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-51. -- Resolution: Won't Fix Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Dropped custom remote muck in favor of using ssh. Generalize the transport access on per-thread bases --- Key: GSHELL-51 URL: https://issues.apache.org/jira/browse/GSHELL-51 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Whisper Affects Versions: 1.0-alpha-1 Reporter: Jason Dillon Fix For: 1.0-alpha-2 Need to generalize how something gets a holf of the current whisper transport. Many different things need it which can not be injected, like JAAS or rfile:// handlers, etc. So we need to provide a _secure_ way to allow these components access to the current transport in use to allow them to communicate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-118) The inter-operation of gshell rsh commands between Sun and IBM JDK failed
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-118.
---
Resolution: Won't Fix
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Dropped custom remote muck in favor of using ssh.
The inter-operation of gshell rsh commands between Sun and IBM JDK failed
-
Key: GSHELL-118
URL: https://issues.apache.org/jira/browse/GSHELL-118
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Remote Shell
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
1. Start rsh-server using Sun JDK in Linux
remote/rsh-server tcp://9.125.143.158:1098
2. Run the following gshell command using IBM JDK in Windows:
remote/rsh tcp://9.125.143.158:1098 geronimo/start-server
In Linux terminal, got the following exception:
{noformat}
14:57:58,347 WARN [RshServer$Handler] [/9.186.117.32:2223] EXCEPTION:
org.apache.mina.filter.codec.ProtocolDecoderException:
org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor (Hexdump: 78
72 01 00 1D 63 6F 6D 2E 69 62 6D 2E 73 65
63 75 72 69 74 79 2E 78 35 30 39 2E 58 35 30 39 4B 65 79 78 70 77 A2 30 81 9F
30 0D 06 09 2A 86 48 86 F7 0D 01 01 01
05 00 03 81 8D 00 30 81 89 02 81 81 00 CE 37 A6 E6 ED 92 2A 37 D2 FA 6E 57 00
86 96 A0 F8 71 87 57 88 77 CA 09 DF 66
50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D 7C C2 20
D6 A3 A0 5A EB DC 0A 95 C6 D3 30 E6 15
02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F 00 28 AE
A0 61 45 0A 16 BE 6B 08 22 0B 8B 21 8D
A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87 31 02 03
01 00 01 78 73 72 01 00 14 6A 61 76 61
2E 6D 61 74 68 2E 42 69 67 49 6E 74 65 67 65 72 78 71 00 7E 00 07 FF FF FF FF
FF FF FF FF FF FF FF FE FF FF FF FE 00
00 00 01 75 72 01 00 02 5B 42 78 70 00 00 00 80 CE 37 A6 E6 ED 92 2A 37 D2 FA
6E 57 00 86 96 A0 F8 71 87 57 88 77 CA
09 DF 66 50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D
7C C2 20 D6 A3 A0 5A EB DC 0A 95 C6 D3
30 E6 15 02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F
00 28 AE A0 61 45 0A 16 BE 6B 08 22 0B
8B 21 8D A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87
31 78 73 71 00 7E 00 0C FF FF FF FF FF
FF FF FF FF FF FF FE FF FF FF FE 00 00 00 01 75 71 00 7E 00 0E 00 00 00 03 01
00 01 78)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor
at org.apache.mina.common.ByteBuffer.getObject(ByteBuffer.java:1530)
at
org.apache.mina.filter.codec.serialization.ObjectSerializationDecoder.doDecode(ObjectSerializationDecoder.jav
a:92)
at
org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:157)
... 12 more
Caused by: java.io.InvalidClassException: failed to read class descriptor
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1567)
at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at
[jira] Updated: (GSHELL-16) New command: ssh
[
https://issues.apache.org/jira/browse/GSHELL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-16:
---
Affects Version/s: 1.0-alpha-2
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Assignee: Jason Dillon
New command: ssh
Key: GSHELL-16
URL: https://issues.apache.org/jira/browse/GSHELL-16
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Commands
Affects Versions: 1.0-alpha-2
Reporter: Jason Dillon
Assignee: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-2
Attachments: GSHELL-16.patch
Create a {{ssh}} command that provides similar functionality to the unix
shell equivalent {{ssh}} (and {{scp}}) commands inside of GShell.
Can wrap the Jsch API to make a ssh command.
Basically, this command will allow a user inside of GShell to make a
connection to a normal {{sshd}} server, run some commands and/or transfer
some files and even setup port forwarding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-119) The set command doesn't work if there is white space beside the equal mark
[
https://issues.apache.org/jira/browse/GSHELL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-119.
---
Resolution: Fixed
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Set syntax is now:
{noformat}
set name value
{noformat}
The set command doesn't work if there is white space beside the equal mark
Key: GSHELL-119
URL: https://issues.apache.org/jira/browse/GSHELL-119
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Commands - Builtins, Parser
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
Run the following command, notice that there is a white space at the left of
the equal mark.
{noformat}
[EMAIL PROTECTED]:/ set password =manager
ERROR RuntimeException: Invalid identifer name:
{noformat}
Run the following command, notice that there is a white space at the right of
the equal mark, the value of variable password is not set correctly.
{noformat}
[EMAIL PROTECTED]:/ set password= manager
[EMAIL PROTECTED]:/ echo $password
[EMAIL PROTECTED]:/
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-72) Externalize command help pages
[
https://issues.apache.org/jira/browse/GSHELL-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-72.
--
Resolution: Fixed
Fix Version/s: (was: 1.0-alpha-3)
1.0-alpha-2
Help pages are in the commands i18n message bundles.
Externalize command help pages
--
Key: GSHELL-72
URL: https://issues.apache.org/jira/browse/GSHELL-72
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Commands, Core
Reporter: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-2
The commands help page (ie. {{help command}}). Should be pulled and
rendered (with ANSI muck) from an resource file. This is seperate than the
syntax help from {{command \-\-help}}... though there should be a way to
include the {{\-\-help}} output in the help page.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-19) New command: vfs/browse
[ https://issues.apache.org/jira/browse/GSHELL-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-19. -- Resolution: Fixed Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Got a plethora of vfs support now, ls, cd, pwd, etc... New command: vfs/browse --- Key: GSHELL-19 URL: https://issues.apache.org/jira/browse/GSHELL-19 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Commands Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-2 Implement a filesystem browser command with VFS to augment the current VFS copy command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-93) The prompter should be given the Session so that it can cusomize the prompt
[ https://issues.apache.org/jira/browse/GSHELL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-93. -- Resolution: Fixed Prompter is now exposed The prompter should be given the Session so that it can cusomize the prompt --- Key: GSHELL-93 URL: https://issues.apache.org/jira/browse/GSHELL-93 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Core Affects Versions: 1.0-alpha-1 Reporter: Guillaume Nodet Assignee: Jason Dillon Fix For: 1.0-alpha-2 Also, the prompter creation is embedded in the DefaultShell and can not be easily changed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-101) Implement command context
[ https://issues.apache.org/jira/browse/GSHELL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-101. --- Resolution: Fixed This is now handled by groups Implement command context - Key: GSHELL-101 URL: https://issues.apache.org/jira/browse/GSHELL-101 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Core Affects Versions: 1.0-alpha-2, 1.0-alpha-3 Reporter: Jason Warner Assignee: Jason Dillon Fix For: 1.0-alpha-2 Attachments: GShell-101.patch Gshell current lacks the ability to change the context from which a command is run. All commands default to running from a root directory. To be able to launch a command without fully qualifying (i.e; /bsf/script), the command search path must be used. It would be nice if we could also changed the context such that we can run any bsf command (or other command group commands) without having to modify the command search path. This will also allow us to use relative command paths (../ and ./). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-121) IllegalArgumentException thrown in LogginProcessorTest
[ https://issues.apache.org/jira/browse/GSHELL-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-121. --- Resolution: Fixed Fix Version/s: 1.0-alpha-2 Thanks! IllegalArgumentException thrown in LogginProcessorTest -- Key: GSHELL-121 URL: https://issues.apache.org/jira/browse/GSHELL-121 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.0-alpha-2 Environment: AIX v5.3 IBM JDK 1.5 Reporter: Jamie goodyear Assignee: Jason Dillon Fix For: 1.0-alpha-2 Attachments: gshell-121.txt IllegalArgumentException thrown in LogginProcessorTest. When running build tests for gshell alpha-2 I get testprocessor(org.apache.geronimo.gshell.spring.LogginProcessorTest) fail. The logs indicates a java.lang.IllegalArgumentException: not support: indent-number. After some research this issue appears to be common. The solution tends to be to wrap calls to setAttribute and setOutputProperty with try/catch (IllegalArgumentException). I'll submit a patch for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-61) Add more options for the help command to display the full tree, current context, etc.
[
https://issues.apache.org/jira/browse/GSHELL-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-61.
--
Resolution: Fixed
The help command has been rewritten
Add more options for the help command to display the full tree, current
context, etc.
-
Key: GSHELL-61
URL: https://issues.apache.org/jira/browse/GSHELL-61
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Commands, Core
Affects Versions: 1.0-alpha-1
Reporter: Jason Dillon
Priority: Minor
Fix For: 1.0-alpha-2
The {{help}} command needs to have more options to limit hat commands are
displayed. For example, by default perhaps only the commands in the current
context should be displayed. Or when given a path, display the commands in
that path, or if it is a command, then display the help for that command.
And also, allow the full tree to be rendered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-56) Re-implement command-line completion
[ https://issues.apache.org/jira/browse/GSHELL-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-56. -- Resolution: Fixed Re-implement command-line completion Key: GSHELL-56 URL: https://issues.apache.org/jira/browse/GSHELL-56 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Components: Commands, Core Affects Versions: 1.0-alpha-1 Reporter: Jason Dillon Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-43) Add role-based layout selection
[ https://issues.apache.org/jira/browse/GSHELL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-43. -- Resolution: Won't Fix Layouts are gone. Add role-based layout selection --- Key: GSHELL-43 URL: https://issues.apache.org/jira/browse/GSHELL-43 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Core Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 Add support to select a different layout based on the user who is logged in. Some users might need only basic commands while others might need a full range (of admin or potentially harmful commands). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-41) Add i18n message support
[ https://issues.apache.org/jira/browse/GSHELL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-41. -- Resolution: Fixed Fix Version/s: (was: 1.0-alpha-3) 1.0-alpha-2 Mostly working now. Add i18n message support Key: GSHELL-41 URL: https://issues.apache.org/jira/browse/GSHELL-41 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support - I18n Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-2 Need to create a simple API to allow commands to _easily_ internationalize messages. Probably need to: * create an annotation injection system for i18n messages * hook up i18n to clp * hook up i18n to prefs * create a rendering system (like the ansi renderer) to insert i18n messages in place of tokens A skeleton project is setup for i18n here: * https://svn.apache.org/repos/asf/geronimo/gshell/trunk/gshell-support/gshell-i18n/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-73) {redirec} does not work with exported content
[
https://issues.apache.org/jira/browse/GSHELL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-73.
--
Resolution: Fixed
Added a {{\{redir\}}} user-macro to inject some javascript to render the notice
+ redirect
{redirec} does not work with exported content
-
Key: GSHELL-73
URL: https://issues.apache.org/jira/browse/GSHELL-73
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Website
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.0-alpha-2
Pages like this have redirects:
* http://cwiki.apache.org/GSHELL/issue-tracking.html
But they don't work on the exported pages,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-120) Consider using JSecurity
Consider using JSecurity Key: GSHELL-120 URL: https://issues.apache.org/jira/browse/GSHELL-120 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-3 http://www.jsecurity.org/docs/quickstart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-117) GShell doesn't support \ in the path in Widnows platform
[
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606681#action_12606681
]
Jason Dillon commented on GSHELL-117:
-
Yes, most certainly there is work left to be done on the interactive shell,
especially related to the syntax parser.
GShell doesn't support \ in the path in Widnows platform
--
Key: GSHELL-117
URL: https://issues.apache.org/jira/browse/GSHELL-117
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: CLI
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Environment: Windows
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Run the following command and get errors in Windows
{noformat}
deploy/deploy H:\FTP_ROOT\Build\cviewer.war
ERROR TokenMgrError: Lexical error at line 1, column 18. Encountered: F
(70), after : \\
{noformat}
It works fine for double slash:
deploy/deploy H:\\FTP_ROOT\\Build\\cviewer.war
It's not convenience for windows users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-67) Allow the clp to generate help text with ANSI colors
[
https://issues.apache.org/jira/browse/GSHELL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606824#action_12606824
]
Jason Dillon commented on GSHELL-67:
This is now up to the CommandDocumenter implementation.
Allow the clp to generate help text with ANSI colors
Key: GSHELL-67
URL: https://issues.apache.org/jira/browse/GSHELL-67
Project: GShell
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Support - CLP
Reporter: Jason Dillon
Priority: Trivial
Fix For: 1.0-alpha-2
Generated {{--help}} text should probably use ANSI to highlight things, and
allow embedded {{|@xxx yyy|}} syntax for implementors to provide specific
coloring.
This basically means using the ANSI renderer in the CLP printer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-117) GShell doesn't support \ in the path in Widnows platform
[
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606499#action_12606499
]
Jason Dillon commented on GSHELL-117:
-
This should only be a problem when running the interactive shell, which isn't
really ready for production use yet.
But from the platform command line this should work fine:
{noformat}
gsh.bat deploy/deploy H:\FTP_ROOT\Build\cviewer.war
{noformat}
The above does not invoke the parser, as the tokens are already split up into a
String[] for the main() invoke.
However, using the -c flag would not:
{noformat}
gsh.bat -c deploy/deploy H:\FTP_ROOT\Build\cviewer.war
{noformat}
Because this will cause the parser to be used to tokenize the input.
GShell doesn't support \ in the path in Widnows platform
--
Key: GSHELL-117
URL: https://issues.apache.org/jira/browse/GSHELL-117
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: CLI
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Environment: Windows
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Run the following command and get errors in Windows
{noformat}
deploy/deploy H:\FTP_ROOT\Build\cviewer.war
ERROR TokenMgrError: Lexical error at line 1, column 18. Encountered: F
(70), after : \\
{noformat}
It works fine for double slash:
deploy/deploy H:\\FTP_ROOT\\Build\\cviewer.war
It's not convenience for windows users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-117) GShell doesn't support \ in the path in Widnows platform
[
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604320#action_12604320
]
Jason Dillon commented on GSHELL-117:
-
FYI, this is because the JavaCC gshell-parser's string handling is based on the
JavaCC java parsers string handling...
GShell doesn't support \ in the path in Widnows platform
--
Key: GSHELL-117
URL: https://issues.apache.org/jira/browse/GSHELL-117
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: CLI
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Environment: Windows
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Run the following command and get errors in Windows
{noformat}
deploy/deploy H:\FTP_ROOT\Build\cviewer.war
ERROR TokenMgrError: Lexical error at line 1, column 18. Encountered: F
(70), after : \\
{noformat}
It works fine for double slash:
deploy/deploy H:\\FTP_ROOT\\Build\\cviewer.war
It's not convenience for windows users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-119) The set command doesn't work if there is white space beside the equal mark
[
https://issues.apache.org/jira/browse/GSHELL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-119:
Component/s: Parser
Affects Version/s: (was: 1.0-beta-1)
(was: 1.0-alpha-3)
Fix Version/s: (was: 1.0-alpha-2)
This is related to the parsers lack of features.
The set command doesn't work if there is white space beside the equal mark
Key: GSHELL-119
URL: https://issues.apache.org/jira/browse/GSHELL-119
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Commands - Builtins, Parser
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Run the following command, notice that there is a white space at the left of
the equal mark.
{noformat}
[EMAIL PROTECTED]:/ set password =manager
ERROR RuntimeException: Invalid identifer name:
{noformat}
Run the following command, notice that there is a white space at the right of
the equal mark, the value of variable password is not set correctly.
{noformat}
[EMAIL PROTECTED]:/ set password= manager
[EMAIL PROTECTED]:/ echo $password
[EMAIL PROTECTED]:/
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-119) The set command doesn't work if there is white space beside the equal mark
[
https://issues.apache.org/jira/browse/GSHELL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-119:
Fix Version/s: 1.0-alpha-3
The set command doesn't work if there is white space beside the equal mark
Key: GSHELL-119
URL: https://issues.apache.org/jira/browse/GSHELL-119
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Commands - Builtins, Parser
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Run the following command, notice that there is a white space at the left of
the equal mark.
{noformat}
[EMAIL PROTECTED]:/ set password =manager
ERROR RuntimeException: Invalid identifer name:
{noformat}
Run the following command, notice that there is a white space at the right of
the equal mark, the value of variable password is not set correctly.
{noformat}
[EMAIL PROTECTED]:/ set password= manager
[EMAIL PROTECTED]:/ echo $password
[EMAIL PROTECTED]:/
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4105) input in gshell gets corrupted after starting server in background
[ https://issues.apache.org/jira/browse/GERONIMO-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603599#action_12603599 ] Jason Dillon commented on GERONIMO-4105: Interesting. Well, the current --background support in start-server is a bit of a hack, the background should really happen at the shell-level which can properly handle setting up the streams for the command. This is pending some parser work, which is desperately needed for more than just this issue. input in gshell gets corrupted after starting server in background -- Key: GERONIMO-4105 URL: https://issues.apache.org/jira/browse/GERONIMO-4105 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.2 Reporter: Jarek Gawor Priority: Critical Using ghsell, once the server is started in background (geronimo/start-server -b), the command line input gets corrupted somehow and every other letter typed is eaten. For example, to actaully perform exit command I had to type eexxiitt. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4093) gsh scripts are not looking for optional setjavaenv script
[ https://issues.apache.org/jira/browse/GERONIMO-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603609#action_12603609 ] Jason Dillon commented on GERONIMO-4093: I still *really, really, really* do not like this change and still would like to see this cruft dropped. gsh scripts are not looking for optional setjavaenv script -- Key: GERONIMO-4093 URL: https://issues.apache.org/jira/browse/GERONIMO-4093 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.2 Reporter: Donald Woods Assignee: Donald Woods Fix For: 2.1.2, 2.2 gsh scripts are not allowing users to provide the optional setjavaenv scripts, like the previous geronimo/deploy scripts allowed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-81) Depdendency on sun.* packages
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-81:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Depdendency on sun.* packages
-
Key: GSHELL-81
URL: https://issues.apache.org/jira/browse/GSHELL-81
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Core
Reporter: Guillaume Nodet
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
It seems that GShell is currently unable to run without the sun.* packages in
the classloader.
The reason is that it uses xstream advanced mode which make use of these
packages.
If these packages are not on the classpath, xstream will default to the pure
java reflection provider which will cause exceptions like the following:
{noformat}
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot
construct org.apache.geronimo.gshell.layout.model.CommandNode as it does not
have a no-args constructor
Debugging information
message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
cause-exception :
com.thoughtworks.xstream.converters.reflection.ObjectAccessException
cause-message : Cannot construct
org.apache.geronimo.gshell.layout.model.CommandNode as it does not have a
no-args constructor
class : org.apache.geronimo.gshell.layout.model.Layout
required-type : org.apache.geronimo.gshell.layout.model.CommandNode
path: /layout/nodes/command
---
{noformat}
I'm not sure if this is a good idea or if we should support that pure java
mode...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-41) Add i18n message support
[ https://issues.apache.org/jira/browse/GSHELL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-41: --- Fix Version/s: (was: 1.0-alpha-2) 1.0-alpha-3 Add i18n message support Key: GSHELL-41 URL: https://issues.apache.org/jira/browse/GSHELL-41 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support - I18n Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 Need to create a simple API to allow commands to _easily_ internationalize messages. Probably need to: * create an annotation injection system for i18n messages * hook up i18n to clp * hook up i18n to prefs * create a rendering system (like the ansi renderer) to insert i18n messages in place of tokens A skeleton project is setup for i18n here: * https://svn.apache.org/repos/asf/geronimo/gshell/trunk/gshell-support/gshell-i18n/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-40) Add annotation-based preferences injection support
[ https://issues.apache.org/jira/browse/GSHELL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-40: --- Fix Version/s: (was: 1.0-alpha-2) 1.0-alpha-3 Add annotation-based preferences injection support -- Key: GSHELL-40 URL: https://issues.apache.org/jira/browse/GSHELL-40 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support - Prefs Reporter: Jason Dillon Priority: Minor Fix For: 1.0-alpha-3 Add a simple annotation-based API to allow the preferences API to be used by commands (similar to how the CLP stuff makes it simple to handle command-line options and arguments). A skeleton project is setup here for the prefs stuff: * https://svn.apache.org/repos/asf/geronimo/gshell/trunk/gshell-support/gshell-prefs/ Probably need to have an annotation for types to denote the prefs node, and then have a preferences annotation with optional node definition for overrides. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-118) The inter-operation of gshell rsh commands between Sun and IBM JDK failed
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602182#action_12602182
]
Jason Dillon commented on GSHELL-118:
-
This is really 2 related problems. The last one is the NPE in the RM, I may
have fixed that already. The first is a problem with the ConnectMessage,
relying on the underlying Java serialization mechanism to do the right thing
with java.security.PublicKey. To fix will have to customize the serialization.
The inter-operation of gshell rsh commands between Sun and IBM JDK failed
-
Key: GSHELL-118
URL: https://issues.apache.org/jira/browse/GSHELL-118
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Remote Shell
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
1. Start rsh-server using Sun JDK in Linux
remote/rsh-server tcp://9.125.143.158:1098
2. Run the following gshell command using IBM JDK in Windows:
remote/rsh tcp://9.125.143.158:1098 geronimo/start-server
In Linux terminal, got the following exception:
{noformat}
14:57:58,347 WARN [RshServer$Handler] [/9.186.117.32:2223] EXCEPTION:
org.apache.mina.filter.codec.ProtocolDecoderException:
org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor (Hexdump: 78
72 01 00 1D 63 6F 6D 2E 69 62 6D 2E 73 65
63 75 72 69 74 79 2E 78 35 30 39 2E 58 35 30 39 4B 65 79 78 70 77 A2 30 81 9F
30 0D 06 09 2A 86 48 86 F7 0D 01 01 01
05 00 03 81 8D 00 30 81 89 02 81 81 00 CE 37 A6 E6 ED 92 2A 37 D2 FA 6E 57 00
86 96 A0 F8 71 87 57 88 77 CA 09 DF 66
50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D 7C C2 20
D6 A3 A0 5A EB DC 0A 95 C6 D3 30 E6 15
02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F 00 28 AE
A0 61 45 0A 16 BE 6B 08 22 0B 8B 21 8D
A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87 31 02 03
01 00 01 78 73 72 01 00 14 6A 61 76 61
2E 6D 61 74 68 2E 42 69 67 49 6E 74 65 67 65 72 78 71 00 7E 00 07 FF FF FF FF
FF FF FF FF FF FF FF FE FF FF FF FE 00
00 00 01 75 72 01 00 02 5B 42 78 70 00 00 00 80 CE 37 A6 E6 ED 92 2A 37 D2 FA
6E 57 00 86 96 A0 F8 71 87 57 88 77 CA
09 DF 66 50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D
7C C2 20 D6 A3 A0 5A EB DC 0A 95 C6 D3
30 E6 15 02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F
00 28 AE A0 61 45 0A 16 BE 6B 08 22 0B
8B 21 8D A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87
31 78 73 71 00 7E 00 0C FF FF FF FF FF
FF FF FF FF FF FF FE FF FF FF FE 00 00 00 01 75 71 00 7E 00 0E 00 00 00 03 01
00 01 78)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor
at org.apache.mina.common.ByteBuffer.getObject(ByteBuffer.java:1530)
at
org.apache.mina.filter.codec.serialization.ObjectSerializationDecoder.doDecode(ObjectSerializationDecoder.jav
a:92)
at
org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:157)
... 12 more
Caused by: java.io.InvalidClassException: failed to read class descriptor
[jira] Commented: (GSHELL-118) The inter-operation of gshell rsh commands between Sun and IBM JDK failed
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602183#action_12602183
]
Jason Dillon commented on GSHELL-118:
-
BTW, for reports like this it would be *very* handy if you ran with {{gsh
--debug}} to provide more context other than the exception.
The inter-operation of gshell rsh commands between Sun and IBM JDK failed
-
Key: GSHELL-118
URL: https://issues.apache.org/jira/browse/GSHELL-118
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Remote Shell
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
1. Start rsh-server using Sun JDK in Linux
remote/rsh-server tcp://9.125.143.158:1098
2. Run the following gshell command using IBM JDK in Windows:
remote/rsh tcp://9.125.143.158:1098 geronimo/start-server
In Linux terminal, got the following exception:
{noformat}
14:57:58,347 WARN [RshServer$Handler] [/9.186.117.32:2223] EXCEPTION:
org.apache.mina.filter.codec.ProtocolDecoderException:
org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor (Hexdump: 78
72 01 00 1D 63 6F 6D 2E 69 62 6D 2E 73 65
63 75 72 69 74 79 2E 78 35 30 39 2E 58 35 30 39 4B 65 79 78 70 77 A2 30 81 9F
30 0D 06 09 2A 86 48 86 F7 0D 01 01 01
05 00 03 81 8D 00 30 81 89 02 81 81 00 CE 37 A6 E6 ED 92 2A 37 D2 FA 6E 57 00
86 96 A0 F8 71 87 57 88 77 CA 09 DF 66
50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D 7C C2 20
D6 A3 A0 5A EB DC 0A 95 C6 D3 30 E6 15
02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F 00 28 AE
A0 61 45 0A 16 BE 6B 08 22 0B 8B 21 8D
A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87 31 02 03
01 00 01 78 73 72 01 00 14 6A 61 76 61
2E 6D 61 74 68 2E 42 69 67 49 6E 74 65 67 65 72 78 71 00 7E 00 07 FF FF FF FF
FF FF FF FF FF FF FF FE FF FF FF FE 00
00 00 01 75 72 01 00 02 5B 42 78 70 00 00 00 80 CE 37 A6 E6 ED 92 2A 37 D2 FA
6E 57 00 86 96 A0 F8 71 87 57 88 77 CA
09 DF 66 50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D
7C C2 20 D6 A3 A0 5A EB DC 0A 95 C6 D3
30 E6 15 02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F
00 28 AE A0 61 45 0A 16 BE 6B 08 22 0B
8B 21 8D A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87
31 78 73 71 00 7E 00 0C FF FF FF FF FF
FF FF FF FF FF FF FE FF FF FF FE 00 00 00 01 75 71 00 7E 00 0E 00 00 00 03 01
00 01 78)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor
at org.apache.mina.common.ByteBuffer.getObject(ByteBuffer.java:1530)
at
org.apache.mina.filter.codec.serialization.ObjectSerializationDecoder.doDecode(ObjectSerializationDecoder.jav
a:92)
at
org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:157)
... 12 more
Caused by: java.io.InvalidClassException: failed to read class descriptor
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1567)
at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
[jira] Closed: (GSHELL-89) Install thread specific System.out and System.err adapters
[ https://issues.apache.org/jira/browse/GSHELL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-89. -- Resolution: Fixed Install thread specific System.out and System.err adapters -- Key: GSHELL-89 URL: https://issues.apache.org/jira/browse/GSHELL-89 Project: GShell Issue Type: Task Security Level: public(Regular issues) Components: Core Reporter: Jarek Gawor Assignee: Jason Dillon Fix For: 1.0-alpha-2 Some integrated tools such as wsgen and wsimport insist on outputting stuff directly to System.out and System.err. So the only way to capture their output is to install System.err/System.out adapters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-118) The inter-operation of gshell rsh commands between Sun and IBM JDK failed
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-118:
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
The inter-operation of gshell rsh commands between Sun and IBM JDK failed
-
Key: GSHELL-118
URL: https://issues.apache.org/jira/browse/GSHELL-118
Project: GShell
Issue Type: Bug
Security Level: public(Regular issues)
Components: Remote Shell
Affects Versions: 1.0-alpha-1, 1.0-alpha-2
Reporter: YunFeng Ma
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
1. Start rsh-server using Sun JDK in Linux
remote/rsh-server tcp://9.125.143.158:1098
2. Run the following gshell command using IBM JDK in Windows:
remote/rsh tcp://9.125.143.158:1098 geronimo/start-server
In Linux terminal, got the following exception:
{noformat}
14:57:58,347 WARN [RshServer$Handler] [/9.186.117.32:2223] EXCEPTION:
org.apache.mina.filter.codec.ProtocolDecoderException:
org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor (Hexdump: 78
72 01 00 1D 63 6F 6D 2E 69 62 6D 2E 73 65
63 75 72 69 74 79 2E 78 35 30 39 2E 58 35 30 39 4B 65 79 78 70 77 A2 30 81 9F
30 0D 06 09 2A 86 48 86 F7 0D 01 01 01
05 00 03 81 8D 00 30 81 89 02 81 81 00 CE 37 A6 E6 ED 92 2A 37 D2 FA 6E 57 00
86 96 A0 F8 71 87 57 88 77 CA 09 DF 66
50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D 7C C2 20
D6 A3 A0 5A EB DC 0A 95 C6 D3 30 E6 15
02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F 00 28 AE
A0 61 45 0A 16 BE 6B 08 22 0B 8B 21 8D
A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87 31 02 03
01 00 01 78 73 72 01 00 14 6A 61 76 61
2E 6D 61 74 68 2E 42 69 67 49 6E 74 65 67 65 72 78 71 00 7E 00 07 FF FF FF FF
FF FF FF FF FF FF FF FE FF FF FF FE 00
00 00 01 75 72 01 00 02 5B 42 78 70 00 00 00 80 CE 37 A6 E6 ED 92 2A 37 D2 FA
6E 57 00 86 96 A0 F8 71 87 57 88 77 CA
09 DF 66 50 94 6A 8B 85 CF 06 75 CA 63 E0 E8 F5 C2 7B 5B 68 FB 87 A1 A0 F4 3D
7C C2 20 D6 A3 A0 5A EB DC 0A 95 C6 D3
30 E6 15 02 76 CA 08 78 C7 F4 73 DC F1 67 23 FE C3 94 9A CB B4 AE 9F 9E A9 7F
00 28 AE A0 61 45 0A 16 BE 6B 08 22 0B
8B 21 8D A8 B4 5E 49 77 73 6A 2D AF B1 5D 80 B2 85 E9 5E 2C 36 38 AB 08 BB 87
31 78 73 71 00 7E 00 0C FF FF FF FF FF
FF FF FF FF FF FF FE FF FF FF FE 00 00 00 01 75 71 00 7E 00 0E 00 00 00 03 01
00 01 78)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:6
48)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.mina.common.BufferDataException:
java.io.InvalidClassException: failed to read class descriptor
at org.apache.mina.common.ByteBuffer.getObject(ByteBuffer.java:1530)
at
org.apache.mina.filter.codec.serialization.ObjectSerializationDecoder.doDecode(ObjectSerializationDecoder.jav
a:92)
at
org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:157)
... 12 more
Caused by: java.io.InvalidClassException: failed to read class descriptor
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1567)
at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at
