Hi Anders,
okay now I understand the problem. This bug is allready fixed for new
projects. There are two ways to fix it. Modify the .classpath or remove
the framework from the classpath with the project properties and it
again with the wolips context menu add system framework.
Please let me know if it work.
Ulrich
Am Dienstag, 21.01.03 um 13:54 Uhr schrieb Anders Peterson:
> That's not the problem!
>
> UNIXClassPath.txt:
>
> WOROOT/Library/Frameworks/JavaEOAccess.framework/Resources/Java/
> javaeoaccess.jar
> WOROOT/Library/Frameworks/JavaEOControl.framework/Resources/Java/
> javaeocontrol.jar
> WOROOT/Library/Frameworks/JavaFoundation.framework/Resources/Java/
> javafoundation.jar
> WOROOT/Library/Frameworks/JavaWebObjects.framework/Resources/Java/
> javawebobjects.jar
> WOROOT/Library/Frameworks/JavaWOExtensions.framework/Versions/A/
> Resources/Java/JavaWOExtensions.jar
> WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/javaxml.jar
> LOCALROOT/Library/Frameworks/QsdBase.framework/Resources/Java/
> qsdbase.jar
> LOCALROOT/Library/Frameworks/QsdCommon.framework/Resources/Java/
> qsdcommon.jar
> LOCALROOT/Library/Frameworks/QsdCoreData.framework/Resources/Java/
> qsdcoredata.jar
> LOCALROOT/Library/Frameworks/SpclExtensions.framework/Resources/Java/
> spclextensions.jar
>
> MacOSClassPath.txt:
>
> WOROOT/Library/Frameworks/JavaEOAccess.framework/Resources/Java/
> javaeoaccess.jar
> WOROOT/Library/Frameworks/JavaEOControl.framework/Resources/Java/
> javaeocontrol.jar
> WOROOT/Library/Frameworks/JavaFoundation.framework/Resources/Java/
> javafoundation.jar
> WOROOT/Library/Frameworks/JavaWebObjects.framework/Resources/Java/
> javawebobjects.jar
> WOROOT/Library/Frameworks/JavaWOExtensions.framework/Versions/A/
> Resources/Java/JavaWOExtensions.jar
> WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/javaxml.jar
> LOCALROOT/Library/Frameworks/QsdBase.framework/Resources/Java/
> qsdbase.jar
> LOCALROOT/Library/Frameworks/QsdCommon.framework/Resources/Java/
> qsdcommon.jar
> LOCALROOT/Library/Frameworks/QsdCoreData.framework/Resources/Java/
> qsdcoredata.jar
> LOCALROOT/Library/Frameworks/SpclExtensions.framework/Resources/Java/
> spclextensions.jar
>
> CLASSPATH.TXT (Windows)
>
> WOROOT\Library\Frameworks\JavaEOAccess.framework\Resources\Java\javaeoa
> ccess.jar
> WOROOT\Library\Frameworks\JavaEOControl.framework\Resources\Java\javaeo
> control.jar
> WOROOT\Library\Frameworks\JavaFoundation.framework\Resources\Java\javaf
> oundation.jar
> WOROOT\Library\Frameworks\JavaWebObjects.framework\Resources\Java\javaw
> ebobjects.jar
> WOROOT\Library\Frameworks\JavaWOExtensions.framework\Versions\A\Resourc
> es\Java\JavaWOExtensions.jar
> WOROOT\Library\Frameworks\JavaXML.framework\Resources\Java\javaxml.jar
> LOCALROOT\Library\Frameworks\QsdBase.framework\Resources\Java\qsdbase.j
> ar
> LOCALROOT\Library\Frameworks\QsdCommon.framework\Resources\Java\qsdcomm
> on.jar
> LOCALROOT\Library\Frameworks\QsdCoreData.framework\Resources\Java\qsdco
> redata.jar
> LOCALROOT\Library\Frameworks\SpclExtensions.framework\Resources\Java\sp
> clextensions.jar
>
> The '/' and '\' are used correctly. The problem is that some paths
> look like this:
>
> UNIX:
>
> WOROOT/Library/Frameworks/JavaWOExtensions.framework/Versions/A/
> Resources/Java/JavaWOExtensions.jar
>
> Mac:
>
> WOROOT/Library/Frameworks/JavaWOExtensions.framework/Versions/A/
> Resources/Java/JavaWOExtensions.jar
>
> Windows:
>
> WOROOT\Library\Frameworks\JavaWOExtensions.framework\Versions\A\Resourc
> es\Java\JavaWOExtensions.jar
>
>
> The inclusion of Versions\A\Resaources in the paths is the problem!
>
> *.framework\Versions\A\Resources\Java\*.jar
>
> As you can see it only happen with some frameworks.
>
> /Anders
>
> On tisdag, jan 21, 2003, at 13:44 Europe/Stockholm, Ulrich Köster
> wrote:
>
>> Hi,
>>
>> about Number 3:
>>
>> MacUnix Classpath has /
>> Windows has \
>> as a separator. At least on MacOSX.
>>
>> It seems to be correct for me.
>>
>> Ulrich
>>
>> Am Dienstag, 21.01.03 um 11:25 Uhr schrieb Anders Peterson:
>>
>>> Hi all,
>>>
>>> I've mentioned all of this before...
>>>
>>> ___________________
>>> 1) The wobuild.properties file created by WOProject/WOLips does not
>>> work on Windows.
>>>
>>> wo.dir.root=C:\Apple
>>> wo.dir.user.home.library.frameworks=C:\\Documents and
>>> Settings\\apete\Local\Library\Frameworks
>>> wo.woroot=C:\Apple
>>> wo.dir.local=C:\Apple\Local
>>> wo.wosystemroot=C:\Apple
>>> wo.dir.user.home.library=C:\\Documents and
>>> Settings\\apete\Local\Library
>>> wo.dir.library=C:\Apple\Library
>>> wo.dir.local.library=C:\Apple\Local\Library
>>> wo.dir.library.frameworks=C:\Apple\Library\Frameworks
>>> wo.dir.local.library.frameworks=C:\Apple\Local\Library\Frameworks
>>> wo.wolocalroot=C:\Apple\Local
>>> wo.dir.system=C:\Apple
>>>
>>> All the single '\' needs to be replaced with double '\\'.
>>>
>>> ___________________
>>> 2) WOLips adds this to the PB.project file:
>>>
>>> FRAMEWORKSEARCH = (
>>> C:\Apple\Local\Library\Frameworks
>>> );
>>>
>>> While PBWO adds this:
>>>
>>> FRAMEWORKSEARCH = ("C:\\Apple\\Local\\Library\\Frameworks");
>>>
>>> The WOLips version does not work - ProjectBuilder, WOBuilder and
>>> other tools can't parse the PB.project file!
>>>
>>> ___________________
>>> 3) When building on Mac you get classpaths like this:
>>>
>>> WOROOT/Library/Frameworks/JavaWebObjects.framework/Resources/Java/
>>> javawebobjects.jar
>>> WOROOT/Library/Frameworks/JavaWOExtensions.framework/Versions/A/
>>> Resources/Java/JavaWOExtensions.jar
>>> WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/
>>> javaxml.jar
>>>
>>> Paths like *.framework/Versions/A/Resources/Java/*.jar are a problem
>>> if you deploy on a different platform.
>>>
>>> ___________________
>>> 4) The Makefile frequently gets out of sync with the PB.project
>>> file. I don't know why, but I think it may be related to (2). WOLips
>>> has behaved very strangely, but I'm uncertain of the actual
>>> consequences. I only know one thing for sure - building with
>>> ProjectBuilder does not work. (It seems the Makefile is updated
>>> after each successful build - not before, and not if it fails.)
>>>
>>>
>>>
>>> (1) is only a problem once. (3) is only a problem when you deploy.
>>> (2) and (4) are major problems. They make it very difficult to work
>>> with WOLips. (2) should be easy to fix (my guess). (1) is important
>>> because it affects all first-time users on Windows.
>>>
>>> /Anders
>>>
>>>
>>>
>>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Tue Jan 21 2003 - 08:01:14 EST