Closed rslemos closed 3 years ago
Thank you for reporting this issue. We will look into it.
@rslemos I published a 1.0.8-SNAPSHOT for the liberty-arquillian artifacts, and a 1.1.8-SNAPSHOT for the arquillian-liberty-dependencies with the fix for this bug.
Release 1.0.8 contains this fix.
After upgrading to
liberty-arquillian-managed
to 1.0.7, I've configured pom.xml to use the newusrDir
property:After this change,
liberty-arquillian-managed
became unable to stop the server. A java process is left dangling (with open ports and files locked).Full output for
λ mvn test-compile liberty:create liberty:install-feature liberty:configure-arquillian failsafe:integration-test failsafe:verify
When
usrDir
property was unavailable, I had to resort to globalserver.env
file, this way:pom.xml
src/main/liberty/local/etc/server.env
Using this configuration with
liberty-arquillian-managed
version 1.0.7 still works fine. The problem seems to have roots inusrDir
property in arquillian.xml.