In THAT case, yeah, you're SOL ... With the exception that it would be
better to pick nothing than the wrong one, which might SORT of work
enough for you to not notice, but that's pretty weak.
For Wonder, maybe we should throw an exception if one of the jars you
declare is missing and just not let you start up until you correct it.
ms
On Feb 21, 2008, at 2:08 PM, Anjo Krank wrote:
> The problem he had was not that he picked the wrong version. It was
> that the deployment system didn't have the /Lib/Fra version.
> HOWEVER, if we fix this, this may only be a problem for the 15 ms
> when if finds that ERX isn't there either...
>
> Cheers, Anjo
>
>
> Am 21.02.2008 um 20:02 schrieb Mike Schrag:
>
>>> *Any* serious deployment should embed frameworks. It may be open
>>> to debate if this includes /Sys/Lib/Fra, but certainly it
>>> includes /Lib/Fra.
>> Well, except that ultimately embedding will follow these same rules
>> and you'd still get the /Lib/Fram version. I stand by the fact
>> that you just shouldn't have the same named frameworks in both
>> places unless you intend one to be the "chosen one".
>>
>> I would say that if you don't want Wonder's JavaWO, just delete
>> it. Just because we package all the frameworks together doesn't
>> necessarily mean you have to use or even install them all. It's a
>> convenience.
>>
>> ms
>>
>
This archive was generated by hypermail 2.0.0 : Thu Feb 21 2008 - 14:13:47 EST