Geert,
I wasn't suggesting which property should be used. My point is that it
should be the same and I do agree that it would be handy to have some
kind of node discovery in place instead of using system properties.
BTW, Maven property been there for over half a year and no one
reporter this inconsistency.
I don't know what you mean by setup differently, all I see is that if
I remove <statistics> elements from tc-config those dirs are created in
the current folder, at least when this stuff is run from Maven.
Also it is really odd, that even if I specify different locations for
those stats folders I still see that huge warning about directory is
already being used when launching L1 and L2 from Maven.
regards,
Eugene
Geert Bevin wrote:
> Imho, unless there's a general mechanism provided through Terracotta
> to uniquely and repeatedly identify individual nodes at startup, this
> can't really be solved. Adding the property by default to
> tc-config.xml when it is only resolved when Maven is used feels a bit
> hackish to me. Btw, the reason why I chose tc.node-name as the
> property name is because we use tc.install-root in the server. So to
> me it looked consistent.
>
> CVT is by default not creating the statistics dirs in the current dir,
> it puts those alongside the log dirs and the data dirs, ie. in
> ${user.home}/terracotta/. Maybe you've got something setup differently
> with Maven that doesn't use the standard default values of the
> tc-config.xml schema? In that case, the values will indeed be empty,
> resulting into the current dir.
>
> On Tue, Mar 25, 2008 at 8:22 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
>
>> Taylor Gautier wrote:
>> > Yes, I agree, good sensible conventions are a good idea. These seem
>> > pretty sensible. Can you file a bug?
>> CDV-677
>>
>>
>>
>> regards,
>> Eugene
>>
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
