Re: WOLips 1.0.0 rc4 - more classpath.txt problems

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Mon Apr 14 2003 - 06:40:47 EDT

  • Next message: Chuck Hill: "Re: Adding a Pre-processing Step to WOProject?"

    Hi Neale,

    Am Montag, 14.04.03 um 12:21 Uhr schrieb Neale Patton:

    > Hi Ulrich,
    >  
    > Yes please. I'd be happy to verify an update. if the file is large or
    > has a .zip extension then our firewall here probably won't let it
    > through... However you can mail it to 'npatton at mac dot com' and I
    > should be able to pick that up no problem.
    It's on the way.
    >  
    > I'll make sure I upgrade my projects to 1.0.0 (i noticed some changes
    > in the names of the framework and application builder classes in the
    > new version).
    It's still possible to use the old builder. To switch to the new
    builder open the project properties page and select WOLips and click
    'Ok'.
    >  
    > Thanks again,
    > neale.

    You're welcome

    Ulrich
    >
    >
    > -----Original Message-----
    > From: Ulrich Köster [mailto:ulric..bjectstyle.org]
    > Sent: 14 April 2003 11:16
    > To: Neale Patton
    > Cc: woproject-de..bjectstyle.org
    > Subject: Re: WOLips 1.0.0 rc4 - more classpath.txt problems
    >
    > Hi Neale,
    >
    > the problem is fixed. Is it okay if I mail you an update for
    > verification. Don't forget to take a look into the 'What's new'
    > section of the WOLips help to update your projects to 1.0.0.
    >
    > Ulrich
    > Am Montag, 14.04.03 um 10:06 Uhr schrieb Neale Patton:
    >
    > Hello,
    >
    > Having upgraded to WOLips 1.0.0 rc4 on Eclipse 2.1 it seems that all my
    > ClassPath files (CLSSPATH.TXT, MacOSClassPath.txt & UnixClassPath.txt) 
    > files aren't being generated correctly. I am running eclipse 
    > on MacOSX 10.2.5.
    >
    > Here's some specific information regarding the problem:
    >
    > Basically all Local frameworks that I've added to my project are 
    > appearing without the LOCALROOT prefix, e.g.
    >
    > # JVM              == java
    > # JVMOptions       ==
    > # JDB              == jdb
    > # JDBOptions       ==
    > # ApplicationClass == Application
    > APPROOT/Resources/Java/
    > APPROOT/Resources/Java/myproject.jar
    >
    > 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/Resources/Java/
    > JavaWOExtensions.jar
    > WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/javaxml.jar
    > /Library/Frameworks/NOLMarketData.framework/Resources/Java/
    > nolmarketdata.jar
    > /Library/Frameworks/NOLMarketDataToolkit.framework/Resources/Java/
    > nolmarketdatatoolkit.jar
    >
    >
    > While this isn't a problem when testing the apps on my MacOSX 
    > development machine, as soon as I move the apps over the the Windows 
    > deployment boxes they fail to start up. Manually editing the 
    > classpath.txt files and prefixing the local frameworks with LOCALROOT 
    > solves the problem. This used to work fine with WOLips 0.9.7 - so I've 
    > reverted to that release.
    >
    > Here's my wobuild.properties file in case that helps.
    >
    > #This file stores the wo specific properties
    > #Mon Apr 14 08:34:11 BST 2003
    > wo.dir.root=/
    > wo.woroot=/
    > wo.dir.user.home.library.frameworks=/Users/neale/Library/Frameworks
    > wo.dir.local=/
    > wo.wosystemroot=/System
    > wo.dir.library=/System/Library
    > wo.dir.user.home.library=/Users/neale/Library
    > wo.dir.local.library=/Library
    > wo.dir.library.frameworks=/System/Library/Frameworks
    > wo.dir.local.library.frameworks=/Library/Frameworks
    > wo.wolocalroot=/
    > wo.dir.system=/System
    >
    > I tested this with a brand new application template generated by the 
    > WOlips wizard and then just added the two local frameworks and did the 
    > build.
    >
    > If you need any more info, please let me know.
    >
    > Many thanks,
    > neale.
    >
    >
    >
    >
    >
    > BBCi at http://www.bbc.co.uk/
    >
    > This e-mail (and any attachments) is confidential and may contain
    > personal views which are not the views of the BBC unless specifically
    > stated.
    > If you have received it in error, please delete it from your system, do
    > not use, copy or disclose the information in any way nor act in
    > reliance on it and notify the sender immediately. Please note that the
    > BBC monitors e-mails sent or received. Further communication will
    > signify your consent to this.
    >
    >
    >
    > BBCi at http://www.bbc.co.uk/
    >
    > This e-mail (and any attachments) is confidential and may contain
    > personal views which are not the views of the BBC unless specifically
    > stated.
    > If you have received it in error, please delete it from your system, do
    > not use, copy or disclose the information in any way nor act in
    > reliance on it and notify the sender immediately. Please note that the
    > BBC monitors e-mails sent or received. Further communication will
    > signify your consent to this.



    This archive was generated by hypermail 2.0.0 : Mon Apr 14 2003 - 06:46:12 EDT