]
Wild Fly commented on WFLY-13016:
---------------------------------
Sorry, I found after opening this issue that the wildfly-core project had its own issue
tracker.
Windows default install of wildfly as a service starts the service in
an inconsistent directory JBOSS_HOME/bin
--------------------------------------------------------------------------------------------------------------
Key: WFLY-13016
URL:
https://issues.redhat.com/browse/WFLY-13016
Project: WildFly
Issue Type: Enhancement
Components: Build System, Server
Affects Versions: 10.0.0.Final
Reporter: Wild Fly
Assignee: Brian Stansberry
Priority: Major
Hi there,
Thanks for the amazing work on Wildfly so far!
I just ran into some configuration issue where I had to migrate a windows jboss server
install to a linux one, with the files included at the root of the server working
directory (java "user.dir" property).
The issue I had was that my linux wildfly server was not finding my files in its working
directory although they were exactly at the same location relative to JBOSS_HOME and my
code was not using absolute path.
After some research concerning the install scripts, I found that when installing wildfly
as a service (ie. in background), each script (common.ps1, wildfly-init*.sh or
service.bat) was specifying the working folder for that service.
And the issue is that it is not consistent across all scripts... well, in fact it is
almost consistent, except for the .bat script which starts the service in JBOSS_HOME/bin
as its working directory whereas the others scripts starts the service in JBOSS_HOME as
its working directory.
I already located the bug at
https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src...
(the others two configurations are here :
https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src...
and there :
https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src...
)
Thanks for taking this remark into account for enhanced cross-platform configuration!