All Ant properties should be passed down in order to allow overriding from the master process, I would think. Is there a reason not to pass them all down? This is how <ant> works.

Also, Sam has asked that build.sysclasspath in particular be passed down, as this his how Gump operates by ensuring *only* the JAR's it wants are available for the build. All dependencies that a project requires (when doing a Gump build) are provided by Gump not by what the project has in its repository - this gives us true continuous integration with the rest of XDoclet dependencies and can alert us if some other project broke XDoclet, or in this case that XDoclet is breaking some other projects build.

Erik


Ara Abrahamian wrote:
Erik, what kind of property should be passed on? The build was just too
big to normally fit in a single process, that's why we start a new
instance of Ant for each module. If some properties (env.blabla?) should
be passed on then let me know which ones and how. I don't any clue how
Gump really works (not yet).

Ara.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:xdoclet-devel-
[EMAIL PROTECTED]] On Behalf Of Erik Hatcher
Sent: Thursday, December 19, 2002 6:27 PM
To: [EMAIL PROTECTED]
Subject: [Xdoclet-devel] [Fwd: Re: Specifying properties from the
command

line?]

There are some Gump issues with XDoclet and overriding properties
being

discussed on the ant-dev list.

Thoughts?

I haven't had a look at <builder> but we should investigate properties
being passed down somehow.

	Erik

-------- Original Message --------
Subject: Re: Specifying properties from the command line?
Date: Fri, 20 Dec 2002 01:30:36 +1100
From: Conor MacNeill <[EMAIL PROTECTED]>
Reply-To: Ant Developers List <[EMAIL PROTECTED]>
To: Ant Developers List <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>

Sam Ruby wrote:
> I would like to specify the version property for xdoclet builds
within

> gump, but apparently the value I specify is overridden.  Any
suggestions
> would be appreciated...
>

Wow, their build is complex. I did a run with the version property
override
and it created two copies of many jars, one with my version and one
with

their version number.

I've had a quick look into it and one definite problem is the module
builder
custom task. This invokes a separate instance of Ant (using exec
classes).

This sub-instance does not inherit any properties from the controlling
ant

build (the one for which you set the version property).

The only sure fire way I can see to control the version is to munge
the

build.properties file before starting the build.

Conor


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>

For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>





-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel





-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to