One of the features in the new classpath plugins is support for
"project frameworks". This lets you define a folder WITHIN your
project to use to locate frameworks. For instance, you could have a
top level Frameworks folder in your Wonder project that contains
Wonder's JavaWOExtensions and NOT have it in /Library. It means you
have to lug around JavaWOExtensions inside your project, but it might
help you isolate things a bit.
ms
On Feb 21, 2008, at 9:37 PM, Brendan Duddridge wrote:
> Our problem with this is we're actively developing two different
> systems. One uses Wonder, the other doesn't. I straddle both
> projects and do the deploys for both. When I do an "Install..." from
> within Eclipse, the MacOSClassPath.txt file will contain a reference
> to JavaWOExtensions in LOCALROOT if it is found there. But this is
> not right for the non-Wonder project as it should be referenced from
> WOROOT. It's ok for the Wonder project though obviously.
>
> I've basically made it a habit to pre-check all my
> MacOSClassPath.txt files after every install, but before I do the
> actual deploy to our remote servers.
>
> ____________________________________________________________________
> Brendan Duddridge | CTO | 403-277-5591 x24 | brenda..lickspace.com
>
> ClickSpace Interactive Inc.
> Suite L100, 239 - 10th Ave. SE
> Calgary, AB T2G 0V9
>
> http://www.clickspace.com
>
> On Feb 21, 2008, at 12:31 PM, Guido Neitzer wrote:
>
>> On 21.02.2008, at 12:19, Anjo Krank wrote:
>>
>>> I'd choose door number 4. As this is not really a problem as both
>>> should be identical and installing Wonder will definitely fix this.
>>
>> Actually, un-installing Wonder from the local install dirs does
>> "fix" it too ... using the Eclipse source versions of Wonder and
>> adding clean up code that removes the stuff from /Library/
>> Frameworks is one way to go there.
>>
>> cug
>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Thu Feb 21 2008 - 21:51:49 EST