ARTEMIS-466 Fix java-opts handling in maven-cli
Previously, java-opts (--java-options argument on the command line) were not passed on to Artemis broker. This broke the client-kickoff example, which relies on this to configure JMX.
This commit is contained in:
parent
6a468b27f8
commit
e041c40ffd
|
@ -105,7 +105,8 @@ if $cygwin ; then
|
||||||
CLASSPATH=`cygpath --windows "$CLASSPATH"`
|
CLASSPATH=`cygpath --windows "$CLASSPATH"`
|
||||||
fi
|
fi
|
||||||
|
|
||||||
exec "$JAVACMD" $JAVA_ARGS \
|
exec "$JAVACMD" ${java-opts} \
|
||||||
|
$JAVA_ARGS \
|
||||||
-Xbootclasspath/a:"$ARTEMIS_HOME/lib/${logmanager}" \
|
-Xbootclasspath/a:"$ARTEMIS_HOME/lib/${logmanager}" \
|
||||||
-Djava.security.auth.login.config="$ARTEMIS_INSTANCE/etc/login.config" \
|
-Djava.security.auth.login.config="$ARTEMIS_INSTANCE/etc/login.config" \
|
||||||
$ARTEMIS_CLUSTER_PROPS \
|
$ARTEMIS_CLUSTER_PROPS \
|
||||||
|
|
Loading…
Reference in New Issue