Bug 15747

Summary:	change tasks (e.g. Ant) to take urls as well as files
Product:	Ant	Reporter:	pklein
Component:	Core tasks	Assignee:	Ant Notifications List <notifications>
Status:	NEW ---
Severity:	enhancement
Priority:	P3
Version:	1.5.1
Target Milestone:	---
Hardware:	Other
OS:	other

Description pklein 2003-01-01 03:57:07 UTC

IMHO, it would be very helpful if the Property task could get its properties 
via a url, e.g., http://devwebsite/projects/common/build.properties
(I suppose there is almost no limit of useful sources from which a Property 
task could draw its data, but this seems pretty straight forward)

also IMHO, it would be useful if an ant file could include another antfile 
elsewhere on the network via url.

Comment 1 Erik Hatcher 2003-01-01 18:17:22 UTC

Also, a satisfactory workaround would be to use the <get> task to pull the contents of a 
URL to a local file and then use it with <property> or <ant>.

Comment 2 Jose Alberto Fernandez 2003-01-02 10:51:39 UTC

Allowing for URLs all the way throughtout will provide the means
for things like:

   ant -u http://devwebsite/projects/common/build.xml -Dbasedir=.

where -u is like -f but for URLs. And this would allow to have build file 
that do everything including getting the source using CVS.

Comment 3 Matt Benson 2005-05-25 20:18:49 UTC

property has supported the url attribute since 1.6.0 . modifying description. 
Ant is close as well.

Comment 4 Jan Mat 2006-07-11 09:59:25 UTC

Loading the buildfile from URL is difficult because of the basedir. That's
discussed on the dev-list.

"include another antfile" would be done via <import>. That doesnt handle URLs
(or ResourceCollections). I think because of the same reasons (import sets a
property to that directory).