[JBoss JIRA] (SRAMP-447) Re-split the installer into EAP 6.1 and 6.3
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-447?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-447:
-----------------------------------
Instead of splitting the installers back up, I'm wondering if we could do something simpler/smarter. At least with respect to S-RAMP, really the only *runtime* difference between EAP 6.1 and 6.3 was the ModeShape distro that the installer pulls down. Everything else, including compile time, IDP, etc. can stay the same.
Knowing that, could we attempt to simply decide, during the installation, what ModeShape distro to grab, based on the EAP instance's full path (assuming it's not renamed and still contains the version within the dir name)? If that fails, fall back on the latest?
Theoretically, that *should* allow S-RAMP to simultaneously support both, but not splitting up the installers in overlord, overlord-commons, and s-ramp.
[~eric.wittmann]/[~objectiser], thoughts?
> Re-split the installer into EAP 6.1 and 6.3
> -------------------------------------------
>
> Key: SRAMP-447
> URL: https://issues.jboss.org/browse/SRAMP-447
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.5.0.Final
>
>
> SRAMP-382 combined EAP 6.1 and 6.3 support. For the most part, that's fine -- no compile issues, etc. However, the installer needs split back up in order to provide the correct ModeShape distro, etc.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-455) use artifact SHA1 computed by ModeShape
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-455:
---------------------------------
Summary: use artifact SHA1 computed by ModeShape
Key: SRAMP-455
URL: https://issues.jboss.org/browse/SRAMP-455
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
As suggested on https://issues.jboss.org/browse/MODE-2221, ModeShape already computes the SHA1 hash for artifacts. We could use that directly, rather than computing on our own.
Note that the hash is a ModeShape-specific extension and not supported by JCR. So, create an SPI and a default impl in the jcr-repo, but override for ModeShape.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-454) CLI Command: Echo
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-454:
-----------------------------------
Summary: CLI Command: Echo
Key: SRAMP-454
URL: https://issues.jboss.org/browse/SRAMP-454
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Shell
Reporter: Eric Wittmann
Assignee: Brett Meyer
Fix For: 0.5.0.Final
Implement a new CLI command that simply takes 1 argument (an arbitrary string) and echos it back. This would be helpful when running a CLI command file.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-453) Exception if using Backspace on CLI password prompt
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-453:
---------------------------------
Summary: Exception if using Backspace on CLI password prompt
Key: SRAMP-453
URL: https://issues.jboss.org/browse/SRAMP-453
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
If you mistype a password in the CLI prompt and hit Backspace 1 too many times, boom.
S-RAMP Password: java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at java.lang.AbstractStringBuilder.insert(AbstractStringBuilder.java:1152)
at java.lang.StringBuilder.insert(StringBuilder.java:336)
at org.jboss.aesh.console.Buffer.write(Buffer.java:319)
at org.jboss.aesh.console.Console.writeChar(Console.java:837)
at org.jboss.aesh.console.Console.writeChars(Console.java:832)
at org.jboss.aesh.console.Console.parseOperation(Console.java:515)
at org.jboss.aesh.console.Console.read(Console.java:452)
at org.overlord.sramp.shell.InteractiveShellCommandReader.promptForPassword(InteractiveShellCommandReader.java:161)
at org.overlord.sramp.shell.ShellContextImpl.promptForPassword(ShellContextImpl.java:172)
at org.overlord.sramp.shell.commands.core.ConnectCommand.promptForPassword(ConnectCommand.java:107)
at org.overlord.sramp.shell.commands.core.ConnectCommand.execute(ConnectCommand.java:67)
at org.overlord.sramp.shell.SrampShell.run(SrampShell.java:102)
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)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-452) Enhance s-ramp CLI property interpolation: support default values
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-452:
-----------------------------------
Summary: Enhance s-ramp CLI property interpolation: support default values
Key: SRAMP-452
URL: https://issues.jboss.org/browse/SRAMP-452
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Shell
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.5.0.Final
Currently the shell supports property interpolation so that variables can be used in CLI command files. This takes the following form (for example):
{code}
connect http://localhost:8080/s-ramp ${username} ${password}
{code}
The CLI can then be invoked like this:
{code}
sramp.sh -f path/to/cli.txt -Dusername=admin -Dpassword=adminp
{code}
This is good, but let's also support optional default values for the variables, like this:
{code}
connect http://localhost:8080/s-ramp ${username:admin} ${password:adminp}
{code}
This will continue to replace ${username} with whatever value is passed via -Dusername=blah. However, if -Dusername is *not* provided, then the default value of 'admin' will be used. This will result in more powerful CLI scripts with commands like this:
{code}
connect ${sramp.endpoint:http://localhost:8080/s-ramp} ${sramp.username:admin} ${sramp.password:adminp}
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months