Antlet namespaces

The following code is extracted from a sample build. It makes 
me wonder if we can add the same namespace handling to the importer task.
This way te don't have to change all antlets and keep the namespace definition
in one central point. 

Ideas?

Michael

<project name="....." default="all" 
	xmlns:retrieve="http://antlet/retrieve"
	xmlns:generate="http://antlet/generate"
	xmlns:build="http://antlet/build"
	xmlns:test="http://antlet/test"
	xmlns:deploy="http://antlet/deploy"
	xmlns:ftest="http://antlet/ftest"
	xmlns:report="http://antlet/report"
	>

	<taskdef file="antlets/retrieve.xml" uri="http://antlet/retrieve" />
	<taskdef file="antlets/generate.xml" uri="http://antlet/generate" />
	<taskdef file="antlets/build.xml"    uri="http://antlet/build" />
	<taskdef file="antlets/test.xml"     uri="http://antlet/test" />
	<taskdef file="antlets/deploy.xml"   uri="http://antlet/deploy" />
	<taskdef file="antlets/ftest.xml"    uri="http://antlet/ftest" />
	<taskdef file="antlets/report.xml"   uri="http://antlet/report" />

... targets to connect general tasks like build / test / deploy 
     to specialized taskdefs....
	
	<target name="clean">
		<retrieve:clean />
		<generate:clean />
		<build:clean />
		<deploy:clean />
		<ftest:clean />
		<report:clean />
	</target>
</project>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click