I'm not sure I'll do it for the first release, but it should be pretty
straightforward to add in afterwards. It already supports frameworks-
in-project, so the API's are all "project aware".
ms
On Feb 21, 2008, at 5:59 PM, Lachlan Deck wrote:
> Agreed... which reminds me: I suggested before WO5.4 came out that
> it'd be nice if WOLips allowed you to set per-project the relevant
> system paths for whichever WO version the project depends on...
>
> That way instead of running a script every time you want to switch
> projects/WO versions (which means down time), it's set and forget.
>
> Worth revisiting for the new classpath management?
>
> On 22/02/2008, at 7:07 AM, Anjo Krank wrote:
>
>> Which is IMO a serious fuckup all in itself, as there is no version
>> info in the jar names and no obvious way set CP ordering.
>>
>> Cheers, Anjo
>>
>> Am 21.02.2008 um 20:57 schrieb Gavin Eadie:
>>
>>> ... and going forward there seems to be no distinction, as I read
>>> it, all frameworks (Apple's, Wonder, yours and mine) are jar'd and
>>> placed in /Library/WebObjects/lib/ .. Gav
>>>
>>> On Feb 21, 2008, at 1:54 PM, Anjo Krank wrote:
>>>> *Any* serious deployment should embed frameworks. It may be open
>>>> to debate if this includes /Sys/Lib/Fra, but certainly it
>>>> includes /Lib/Fra.
>
> with regards,
> --
>
> Lachlan Deck
This archive was generated by hypermail 2.0.0 : Thu Feb 21 2008 - 18:45:04 EST