Hi Pierre,
I've played a little bit with it.
You have to set the order in the properties page. Right click on the
project root. Select 'properties', 'java build path' and 'order and
export'. Move the libs up and down.
WOLips collects them under there roots:NEXT_SYSTEM_ROOT and
NEXT_LOCAL_ROOT (WOROOT and LOCALROOT in the classpath.txt). To change
the order of the different roots modify your build.xml:
<frameworks root="${wo.wolocalroot}">
<patternset>
<includesfile name="ant.frameworks.wo.wolocalroot"/>
</patternset>
</frameworks>
<frameworks root="${wo.wosystemroot}">
<patternset>
<includesfile name="ant.frameworks.wo.wosystemroot"/>
</patternset>
</frameworks>
Please take a look in my previous post to make sure that the update to
1.0.0 (1.0.1)was correct.
Ulrich
Am Mittwoch, 30.04.03 um 17:32 Uhr schrieb Pierre Bernard:
> Hi Ulrich!
>
> Actually I meant 0.9.8, not 0.9.7. I had updated my projects from
> 0.9.7 to 0.9.8 quite some time ago and guess this was OK as I used
> WOLips 0.9.8 for quite some time with no problems.
>
> Setting the order in the project's 'java build path' indeed changes
> the order of entries in the .classpath file. The order of entries in
> UNIXClassPath.txt however remains unaffected. I even tried trashing
> the full *.woa directory and rebuilding the project to no avail.
>
> My UNIXClassPath.txt still has Windows style path entries sorted
> alphabetically. A colleague using WOLips 0.9.8 has enties realtive to
> Apple variables (LOCALROOT or the like), but can't influence the order
> of entries in the file either.
>
> P.S: I am currently downloading WOLips 1.0.1 and hope to get around to
> testing this and the *.d2wmodel bug against it on friday.
>
> Pierre.
>
> -----Original Message-----
> From: Ulrich Köster [mailto:ulric..bjectstyle.org]
> Sent: Wednesday, April 30, 2003 5:13 PM
> To: Pierre Bernard
> Cc: woproject-de..bjectstyle.org
> Subject: Re: Order of classpath entries in *ClassPath.txt file
>
> Hi Pierre,
>
> take a look in the WOLips help. The 'What's new' section talks about
> the steps to update your projects from 0.9.7 to 0.9.8 and beyond.
>
> To make sure that everything is correct add a local and a system
> framework to your project. The wizards are available in the WOLips
> context menu. After that open the .classpath file in a text editor and
> compare the added frameworks with your entries. I think the file is
> self explaining. The .classpath file is only visible in the navigator
> in the resource view.
>
>
> You can change the order of the libs in the project properties under
> 'java build path' -> 'order and export'. The entries in the classpath
> should get in the classpath.txt in the same order. I've never tried
> it. Please let us know if works for you.
>
>
> Ulrich
>
> Am Mittwoch, 30.04.03 um 16:57 Uhr schrieb Pierre Bernard:
>
> Hi!
>
> I am wondering how WOLips determines the order in which to put the
> classpath entries in the generated classpath files. The files used by
> the laucnh scripts. I would like to modify that order so that I can
> override a few classes with patched versions.
>
> Looking at the generated files makes me think that the entries are
> sorted alphabetically by full path. This does not make much sense,
> Indeed it would be much more sensible to respect the classpath order
> used at build time. I would actually even prefer for the
> *ClassPath.txt files to respect the order of entries in the PB.project
> file.
>
> BTW, on my Windows machine I see that with WOLips 1.0.0 the generated
> UNIXClassPath.txt file contains full Windows file path (e.g.
> D:\SomeFolder\...): This is not going to be good at deployment. Did I
> do something wrong or is this a bug introduced between WOLips 0.9.7 &
> 1.0.0?
>
> Best regards,
> Pierre Bernard
>
>
> **********************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender
> of this message. (Pierre.Bernar..cl.lu)
> This email message has been checked for the presence of computer
> viruses; however this protection does not ensure this message is
> virus free.
> Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
> **********************************************************************
>
>
>
> **********************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender
> of this message. (Pierre.Bernar..cl.lu)
> This email message has been checked for the presence of computer
> viruses; however this protection does not ensure this message is
> virus free.
> Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
> **********************************************************************
This archive was generated by hypermail 2.0.0 : Wed Apr 30 2003 - 11:59:55 EDT