Description of problem: The jboss-as-cp command ends with instructions on how to start the user instance. However, once this terminal goes away, the user might forget the command to start the instance. The jboss-as-cp script should create a startup script in the bin directory of the user instance. This script would simply execute the command that is currently listed in stdout upon executing jboss-as-cp. Version-Release number of selected component (if applicable): 7.1.1-2.fc17-noarch Let's assume the instance is created using the following command: jboss-as-cp -l $HOME/jboss-as-user-instance -c standalone-web.xml Here is a possible implementation of this script: #!/bin/sh DIRNAME=`dirname "$0"` JBOSS_BASE_DIR=$DIRNAME/.. /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml This script would be written located here: $HOME/jboss-as-user-instance/bin/standalone.sh
That's a very good idea! I'm on it.
Fixed in upstream: https://github.com/fedora-jboss-as/jboss-as-rpm/commit/503dc8cbb3953a25efb3204155d5e68f231c8b29 It'll be available in jboss-as-7.1.1-4.
jboss-as-7.1.1-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/jboss-as-7.1.1-4.fc17
jboss-as-7.1.1-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.