Hi Kai,
if you use the incremental builder there is no need to update your
build.xml. Anyway it's worth to take a look at it. The ant.* files are
generated whenever you change the classpath in Eclipse. You may wan't
to use these files with your build.xml. No need to maintain the
classpath twice.
Now to your performance problem:
Is Eclipse launched with 1.4.1 or 1.3.1 did you try to increment the
amount of memory -> Xms and Xmx?
I use Eclipse with the swt from 3.0M3. The results from 'open .java
file' TM benchmark on a cube 450 MHZ: under 2 seconds.
Could you doublecheck that this is with the final of 2.1.1. There was a
bugreport with your issue that is fixed in 2.1.1.
The place was right. I mean the stuff under 1.0.2. Anyway that doesn't
matter with the incremental builder.
Ulrich
On Sonntag, 20. Juli 2003, at 18:29 Uhr, Kaj Hejer wrote:
> At 13:20 +0200 20-07-2003, Ulrich Köster wrote:
>> Hi Kaj,
>>
>> are the build.xml files uptodate? If not take a look in the 'What's
>> new' section of the WOLips help to update your projects to 1.0.4.
>>
>
>
> Hi!
>
> Thanks for answering!
>
> No, I havn't updated the build.xml file since I'm using incremental
> build. Do I need to change to build.xml file even if I use the
> incremental builder?
>
> (We have made our own build.xml file for building WO project using
> woproject.jar so I don't use the build.xml WOLips generate for me.
> The build.xml we use is customized to fit our needs in both
> development and deployment.)
>
> I tried to look for "What's new" in the WOLips help, but there I only
> found the following:
>
> * This update fixes a minor problem in the incremental builder and
> a
> problem with referenced patternsets.
> * Patched org.eclipse.ant.core plugin for Eclipse 2.1.0 and 2.1.1.
> * Updated Ant tasks to support split install.
>
>
> on .../help/topic/org.objectstyle.wolips/doc_root/history.html
>
> I guess I'm not looking at the right place.
>
>
>
> -Kaj :)
This archive was generated by hypermail 2.0.0 : Sun Jul 20 2003 - 12:52:33 EDT