<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Brian Stansberry píše v Po 13. 02. 2012 v 10:30 -0600:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
...
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.
</PRE>
</BLOCKQUOTE>
Nice, that would help in the testsuite scenario.<BR>
<BR>
O.
<PRE>
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 2/13/12 4:28 AM, Ondřej Žižka wrote:
> I've created a jira for this task,
> let's discuss there.
>
> Thx,
> Ondra
>
>
> Ondřej Žižka píše v Po 13. 02. 2012 v 11:15 +0100:
>> Hi Brian,
>>
>> what was the reason to restrict AS config in sys prop to 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.
>>
>> Thanks,
>> Ondra
>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>