[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.... ]
Eric Wittmann edited comment on SRAMP-408 at 4/25/14 8:58 AM:
--------------------------------------------------------------
Tab completion for the "property" command doesn't work as expected. If I type "property " and then hit tab, I get the list of sub-commands as expected. However if I then type "s" (for the 'set' sub-command) and hit tab I get this:
{code}
s-ramp> property
set unset
s-ramp> property s set
{code}
This same problem happens for the "classification" command:
{code}
s-ramp> classification
clear remove add
s-ramp> classification r remove
{code}
was (Author: eric.wittmann):
Tab completion for the "property" command doesn't work as expected. If I type "property " and then hit tab, I get the list of sub-commands as expected. However if I then type "s" (for the 'set' sub-command) and hit tab I get this:
{code}
s-ramp> property
set unset
s-ramp> property s set
{code}
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
> Key: SRAMP-408
> URL: https://issues.jboss.org/browse/SRAMP-408
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion. For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-408:
-------------------------------------
Tab completion for the "property" command doesn't work as expected. If I type "property " and then hit tab, I get the list of sub-commands as expected. However if I then type "s" (for the 'set' sub-command) and hit tab I get this:
{code}
s-ramp> property
set unset
s-ramp> property s set
{code}
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
> Key: SRAMP-408
> URL: https://issues.jboss.org/browse/SRAMP-408
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion. For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-388) Use jboss version of javax.servlet GAV consistently
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-388:
--------------------------------
Description:
EAP uses the GAV
{code}
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
</dependency>
{code}
rather than
{code}
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</dependency>
{code}
This GAV is also available in the community BOM.
We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.
was:
EAP uses the GAV
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
</dependency>
rather than
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
This GAV is also available in the community BOM.
We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.
> Use jboss version of javax.servlet GAV consistently
> ---------------------------------------------------
>
> Key: SRAMP-388
> URL: https://issues.jboss.org/browse/SRAMP-388
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
>
> EAP uses the GAV
> {code}
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.0_spec</artifactId>
> </dependency>
> {code}
> rather than
> {code}
> <dependency>
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> </dependency>
> {code}
> This GAV is also available in the community BOM.
> We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-388) Use jboss version of javax.servlet GAV consistently
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-388:
--------------------------------
Description:
EAP uses the GAV
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
</dependency>
rather than
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
This GAV is also available in the community BOM.
We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.
was:
EAP uses the GAV
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
</dependency>
rather than
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
This GAV is also available in the community BOM. Can we standardise on using that please?
> Use jboss version of javax.servlet GAV consistently
> ---------------------------------------------------
>
> Key: SRAMP-388
> URL: https://issues.jboss.org/browse/SRAMP-388
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
>
> EAP uses the GAV
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.0_spec</artifactId>
> </dependency>
> rather than
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> This GAV is also available in the community BOM.
> We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-388) Use jboss version of javax.servlet GAV consistently
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-388:
-----------------------------------
Assignee: David virgil naranjo (was: Eric Wittmann)
> Use jboss version of javax.servlet GAV consistently
> ---------------------------------------------------
>
> Key: SRAMP-388
> URL: https://issues.jboss.org/browse/SRAMP-388
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
>
> EAP uses the GAV
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.0_spec</artifactId>
> </dependency>
> rather than
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> This GAV is also available in the community BOM. Can we standardise on using that please?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-408:
-------------------------------------
When I use tab completion for the "query" command it adds an extra space at the end of the line. For example (with brackets added to illustrate where the space is):
{code}
[s-ramp> query "/s-ramp/ ]
{code}
So when I type "query" and then a space and then hit tab I get the above, with that additional space at the end. This is problematic because I then have to hit backspace once and *then* continue typing my query.
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
> Key: SRAMP-408
> URL: https://issues.jboss.org/browse/SRAMP-408
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion. For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-408:
-------------------------------------
Tab completion for commands like getContent and getMetaData aren't completing properly. If I have a valid query/feed in my context, the tab completion properly lists out all of the "feed:N" options but it doesn't actually insert "feed:" at the end of the line.
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
> Key: SRAMP-408
> URL: https://issues.jboss.org/browse/SRAMP-408
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion. For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-410) Shell: file completer not working well
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-410:
-----------------------------------
Summary: Shell: file completer not working well
Key: SRAMP-410
URL: https://issues.jboss.org/browse/SRAMP-410
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: David virgil naranjo
Fix For: 0.5.0 - API Management
The file completer isn't working properly. It should be thoroughly tested and fixed. Please note that it should be tested on both Linux and Windows, since path separators are different in those file systems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-408:
-------------------------------------
With the latest changes, I am still seeing a few problems. For example:
{code}
s-ramp> s-ramp:up
s-ramp:updateContent s-ramp:updateMetaData s-ramp:upload
s-ramp> s-ramp:upload java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
at java.util.ArrayList$Itr.next(ArrayList.java:831)
at org.overlord.sramp.shell.util.FileNameCompleter.complete(FileNameCompleter.java:102)
at org.overlord.sramp.shell.commands.core.UploadArtifactCommand.tabCompletion(UploadArtifactCommand.java:139)
at org.overlord.sramp.shell.TabCompleter.complete(TabCompleter.java:87)
at org.jboss.aesh.console.Console.complete(Console.java:1155)
at org.jboss.aesh.console.Console.parseOperation(Console.java:550)
at org.jboss.aesh.console.Console.read(Console.java:452)
at org.overlord.sramp.shell.InteractiveShellCommandReader.readLine(InteractiveShellCommandReader.java:90)
at org.overlord.sramp.shell.AbstractShellCommandReader.read(AbstractShellCommandReader.java:93)
at org.overlord.sramp.shell.SrampShell.run(SrampShell.java:98)
at org.overlord.sramp.shell.SrampShell.main(SrampShell.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:744)
s-ramp>
alias archive: audit: maven: ontology: s-ramp:
s-ramp>
{code}
> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
> Key: SRAMP-408
> URL: https://issues.jboss.org/browse/SRAMP-408
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion. For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (SRAMP-409) Overlord commons Messages
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-409:
------------------------------------------
Summary: Overlord commons Messages
Key: SRAMP-409
URL: https://issues.jboss.org/browse/SRAMP-409
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Create a new project in Overlord-commons called overlord-commons-messages.
Then use this Messages abstraction in S-ramp and dtgov. In case necessary, in these projects extends the CommonMessages functionality and customize it.
Also add the overlord-commons-messages to the project overlord-commons-ant and use it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months