[
https://issues.jboss.org/browse/WFCORE-1187?page=com.atlassian.jira.plugi...
]
Vratislav Marek commented on WFCORE-1187:
-----------------------------------------
I try to reproduce this issue by steps in the description but commands it's out of
date.
Command "_start-embedded-server_" is replaced by "_embed-server_".
In run from a current build from master branch, command "_embed-server_"
unrecognize argument "_--jboss-home_".
{code:java}
[disconnected /] embed-server
--jboss-home="/tmp/2019-01-25/WFCORE-1187/firstLog"
Unrecognized arguments: [--jboss-home]
{code}
But in command help is written like a valid argument.
{code:java}
[disconnected /] help embed-server
SYNOPSIS
embed-server [--admin-only=true|false]
[-c=config_file || --server-config=config_file]
[--empty-config --remove-existing-config]
[--jboss-home=rootdir]
[--stdout=discard|echo]
DESCRIPTION
Launches a standalone server embedded in the CLI process.
ARGUMENTS
...
--jboss-home - Filesystem path pointing to the root directory
of the installation from which the embedded server
should run. Only available if the CLI itself
is not running in a modular classloading environment.
In a non-modular classloading environment, if this
option is not specified, the value of the
environment variable JBOSS_HOME will be used.
Must be specified if the environment variable
JBOSS_HOME is not set.In a modular classloading
environment it is assumed the CLI is running from
the server installation itself and the JBOSS_HOME
environment variable must be set.
...
{code}
Embedded server start / stop / start with new --jboss-home continues
to refer to previous server.log
----------------------------------------------------------------------------------------------------
Key: WFCORE-1187
URL:
https://issues.jboss.org/browse/WFCORE-1187
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Ken Wills
Assignee: ehsavoie Hugonnet
Priority: Major
- start-embedded-server --jboss-home=/foo/bar1
- stop-embedded-server
- start-embedded-server --jboss-home=/foo/bar2
-- server.log in /foo/bar1/standalone/logs/server.log is still written to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)