On Sep 19, 2006, at 3:01 AM, Chris Gray wrote:
On Monday 18 September 2006 18:14, Geir Magnusson Jr. wrote:
Pavel Pervov wrote:
Tried it on Windows and found the problem which, as it looks
like, have
never been caught before.
As I discovered, launcher uses platform specific line separators
to parse
harmonyvm.properties on a specific platform. But
haromynvm.properties,
which
is copied into deploy, has unix line endings and is skipped. As the
result, EM can't initialize.'
A ha!
I workarounded this by running unix2dos on harmonyvm.properties.
Ok - we should get that in as eol-native
Wouldn't it be better (and safer) to fix the parser? Normally a
properties
file can contain any kind of line separators and still be parsed
correctly,
which is a Good Thing IMHO. E.g. according to the spec for
java.util.Properties.load(),
A natural line of input is terminated either by a set of line
terminator
characters (\n or \r or \r\n) or by the end of the file.
Yes - and I think there is a patch somewhere. But we should keep
little nits like this under control.
geir
Chris
--
Chris Gray /k/ Embedded Java Solutions BE0503765045
Embedded & Mobile Java, OSGi http://www.k-embedded-java.com/
[EMAIL PROTECTED] +32 3 216 0369
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
