[ https://issues.jboss.org/browse/AS7-5583?page=com.atlassian.jira.plugin.s... ] Michal Matloka updated AS7-5583: -------------------------------- Description: Currently the only way to specify server port is to edit server configuration .xml. However there are cases which could use definition via jvm arg. Forums shows the following workaround (https://community.jboss.org/thread/168140). I'd like to propose to include in default jboss-as standalone.xml configuration, properties for the most important parameters: eg. change <socket-binding name="http" port="8080"/> to <socket-binding name="http" port="${jboss.http.port:8080}"/> Then would be possible to run jboss on different port via jvm arg ./bin/standalone.sh --server-config=standalone-ha.xml -Djboss.http.port=8888 Solving this issue is important, because some other issues relies on it: eg. https://issues.jboss.org/browse/AS7-1036 With this change, solving mentioned ticket would be very easy, and will allow to run arquillian tests directly on jboss downloaded and unpacked via maven goal, and then managed directly via arquillian (it is the only way to run arquillian tests in some environments, however often 8080 port is already used). I'm willing to solve this feature by myself, however I'd like to hear opinions from other people. was: Currently the only way to specify server port is to edit server configuration .xml. However there are cases which could use definition via jvm arg. Forums shows the following workaround (https://community.jboss.org/thread/168140). I'd like to propose to include in default jboss-as standalone.xml configuration, properties for the most important parameters: eg. change <socket-binding name="http" port="8080"/> to <socket-binding name="http" port="${jboss.http.port:8080}"/> Then would be possible to run jboss on different port via jvm arg ./bin/standalone.sh --server-config=standalone-ha.xml -Djboss.http.port=8888 Solving this issue is important, because some other issues relies on it: eg. https://issues.jboss.org/browse/AS7-1036 With this change, solving mentioned ticket would be very easy, and will allow to run arquillian tests directly on jboss downloaded and unpacked via maven goal, and then managed directly via arquillian. I'm willing to solve this feature by myself, however I'd like to hear opinions from other people. Forum Reference: http://community.jboss.org/thread/168140 (was: http://community.jboss.org/thread/168140) -- 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

[ https://issues.jboss.org/browse/AS7-5583?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-5583: ----------------------------- Component/s: Build System Domain Management Forum Reference: https://community.jboss.org/message/610603#610603, http://community.jboss.org/thread/168140 (was: https://community.jboss.org/message/610603#610603, http://community.jboss.org/thread/168140) -- 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