[
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 don't pretend to have a full understanding of all of the impacts of this
decision, but I would like to throw in a relevant (though somewhat
tangential) value judgment about our approach to the ant support in Eclipse
and how it relates to Eclipse's own build process.
As an ant user, not an eclipse committer, having stable ant execution is
more valuable to me by far than having clever eclipse-specific tasks. One of
the key values of an build is that allows an application to be built
regardless of the IDE used by an individual developer. There are a number of
cases in which we've opted to provide special function for the sake of
integration with Eclipse that have negative impacts on the portability of
ant builds. This, I think, is generally a mistake.
One of the ironic side-effects of our eat-your-own-dog-food approach to
Eclipse development is that we have a homogenous environment from a
development tooling approach. In my experience, this homogeneity is very
unusual. If we want to live by the spirit of eat-your-own-dog-food we'll
move away from using Eclipse to perform all of our builds and rely more
heavily on ant--without the benefit of special IDE specific privileges. This
is the way the rest of the community lives. It may seem like an artificial
constraint to the Eclipse committers, but I think this is a case where we
need to take the "fair play rule" seriously particularly since it may not
feel entirely natural to us.
John-Mason Shackelford
Software Developer
Pearson Educational Measurement - eMeasurement Group
2510 North Dodge St.
Iowa City, IA 52245
ph. 319-354-9200x6214
john-mason.shackelford@xxxxxxxxxxx
http://etest.ncspearson.com
-----Original Message-----
From: platform-ant-dev-admin@xxxxxxxxxxx
[mailto:platform-ant-dev-admin@xxxxxxxxxxx] On Behalf Of Darin Wright
Sent: Friday, March 05, 2004 1:36 PM
To: platform-ant-dev@xxxxxxxxxxx
Subject: 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
_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
