[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ant-dev] Ant project builders in separate VM?
|
I also vote to leave builders in the same VM. If the community feels
otherwise, they should speak up.
Darin
Darin Swanson <Darin_Swanson@xxxxxxxxxx>
Sent by: platform-ant-dev-admin@xxxxxxxxxxx
03/05/2004 01:25 PM
Please respond to
platform-ant-dev
To
platform-ant-dev@xxxxxxxxxxx
cc
Subject
Re: [platform-ant-dev] Ant project builders in separate VM?
Bob is correct that by default these tasks would not work.
But we have added support to annotate Ant task, type, property and extra
classpath entry contributions whether or not they require the Eclipse
runtime to be relevant (or to just plain work).
See http://bugs.eclipse.org/bugs/show_bug.cgi?id=47901
My feeling is to leave builders to run in the same VM...but I am open to
be convinced otherwise.
Darins
Bob Foster <bob@xxxxxxxxxx>
Sent by: platform-ant-dev-admin@xxxxxxxxxxx
03/05/04 10:56 AM
Please respond to platform-ant-dev
To: platform-ant-dev@xxxxxxxxxxx
cc:
Subject: Re: [platform-ant-dev] Ant project builders in
separate VM?
Jared Burns wrote:
> Now that Ant in a separate VM can run in the foreground, should we
change the
> default VM setting for project builders? This would save a lot of people
from
> the memory leakage that they'll get otherwise.
>
> Or am I forgetting something?
How about plugins written to add tasks to Ant when run in Eclipse? Would
this mean they wouldn't work by default?
Bob
_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
