You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Stefano Mazzocchi <st...@apache.org> on 2006/11/24 21:38:50 UTC
Re: [jira] Commented: (HARMONY-2135) DaCapo eclipse fails with java.security.NoSuchAlgorithmException
for an algorithm known to exist
Alexey Varlamov (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/HARMONY-2135?page=comments#action_12452379 ]
>
> Alexey Varlamov commented on HARMONY-2135:
> ------------------------------------------
>
> If the root cause of this is really as described HARMONY-2163, it sounds more like a bug in the DaCapo itself...
uh? are you seriously suggesting that that when dacapo works on all
other VMs and fails on harmony, it's its fault?
I suggest otherwise: there is clearly something that that test triggers
(in harmony's classloaders or somewhere else) that behaves differently
from RI and the other compatible VMs. Let's find out what it is, create
a test that reproduces it and fix it.
--
Stefano.
Re: [jira] Commented: (HARMONY-2135) DaCapo eclipse fails with java.security.NoSuchAlgorithmException
for an algorithm known to exist
Posted by Stefano Mazzocchi <st...@apache.org>.
Alexey Varlamov wrote:
> Agreed, I took causing problem too wide. Well, at least my sentence
> triggered fruitful discussion on dev-list and Tim suggested nice fix.
Agreed.
My point is that it's easy to say "it's their fault" but it's way more
productive (and appears less defensive) to think it's always harmony's
fault unless proved otherwise.
It also makes this community appear way more humble and friendly,
something that doesn't happen on its own, but we all, as a group and as
individuals, have to care for.
--
Stefano.
Re: [jira] Commented: (HARMONY-2135) DaCapo eclipse fails with java.security.NoSuchAlgorithmException for an algorithm known to exist
Posted by Alexey Varlamov <al...@gmail.com>.
Agreed, I took causing problem too wide. Well, at least my sentence
triggered fruitful discussion on dev-list and Tim suggested nice fix.
2006/11/25, Stefano Mazzocchi <st...@apache.org>:
> Alexey Varlamov (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/HARMONY-2135?page=comments#action_12452379 ]
> >
> > Alexey Varlamov commented on HARMONY-2135:
> > ------------------------------------------
> >
> > If the root cause of this is really as described HARMONY-2163, it sounds more like a bug in the DaCapo itself...
>
> uh? are you seriously suggesting that that when dacapo works on all
> other VMs and fails on harmony, it's its fault?
>
> I suggest otherwise: there is clearly something that that test triggers
> (in harmony's classloaders or somewhere else) that behaves differently
> from RI and the other compatible VMs. Let's find out what it is, create
> a test that reproduces it and fix it.
>
> --
> Stefano.
>
>
Re: [jira] Commented: (HARMONY-2135) DaCapo eclipse fails with java.security.NoSuchAlgorithmException
for an algorithm known to exist
Posted by Tim Ellison <t....@gmail.com>.
Stefano Mazzocchi wrote:
> Alexey Varlamov (JIRA) wrote:
>> [ http://issues.apache.org/jira/browse/HARMONY-2135?page=comments#action_12452379 ]
>>
>> Alexey Varlamov commented on HARMONY-2135:
>> ------------------------------------------
>>
>> If the root cause of this is really as described HARMONY-2163, it sounds more like a bug in the DaCapo itself...
>
> uh? are you seriously suggesting that that when dacapo works on all
> other VMs and fails on harmony, it's its fault?
>
> I suggest otherwise: there is clearly something that that test triggers
> (in harmony's classloaders or somewhere else) that behaves differently
> from RI and the other compatible VMs. Let's find out what it is, create
> a test that reproduces it and fix it.
Agreed. I think we have fixed it via HARMONY-2163. Still awaiting
verification.
Regards,
Tim
--
Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.