[
https://issues.jboss.org/browse/AS7-3726?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3726:
-----------------------------------
Brian about the "relative path only" behavior:
{quote}
It was removed because the semantic was unclear. Users were expecting to
pass in an absolute file and then have the AS write back to that file.
We're not going to support writing outside the configuration/ dir and
never intended to.
I agree though that completely eliminating this was not the best
solution, as there's a good use case for it. Besides the testing issue,
some folks don't like the AS overwriting the config file in the first
place, so passing in a config file in a non-writable location is a
workaround solution for them.
My thoughts on this were to allow an --initial-server-config (for
standalone) and --initial-domain-config and --initial-host-config (for
domain). They would allow absolute paths. Their names and documentation
would indicate their contents are read when the process is first started
and thereafter are ignored.
{quote}
TS: Pass the path to docs/examples to the tests.
------------------------------------------------
Key: AS7-3726
URL:
https://issues.jboss.org/browse/AS7-3726
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Original Estimate: 2 hours
Remaining Estimate: 2 hours
In AS7, the path to the config file, passed in a system property, is only allowed to be a
relative path.
In the testsuite, we would make use of absolute paths.
The reason is that we reuse the configs from docs/examples, and they change quite often,
so having them in resources would be hardly maintainable.
However, docs/examples is not guaranteed to be always in the same place: E.g. for EAP,
or for RPM-based installation of EAP it might end up in /var/docs or such.
I would like to pass some property from maven to the tests, but that results in absolute
path.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira