sf-tourl now handles <path> inline

FYI, a small change has just gone into the URL creation task, so that 
you can put a path inline

     <sf-tourl property="codebase">
       <fileset file="${target.jar}"/>
       <fileset file="${test.jar}"/>
       <path refid="libraries.path"/>
     </sf-tourl>

goes to something like

codebase=file:/home/slo/Projects/SmartFrog/Forge/core/components/xml/build/dist/lib/sf-xml.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/components/xml/build/dist/lib/sf-xml-test.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/lib/xerces/jars/xercesImpl-2.6.2.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/lib/xerces/jars/xmlParserAPIs-2.6.2.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/lib/xom/jars/xom-1.1d2.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/lib/jaxen/jars/jaxen-1.0-FCS-full.jar 
file:/home/slo/Projects/SmartFrog/Forge/core/lib/junit/jars/junit-3.8.1.jar

This goes hand in hand with the new repository stuff in ant1.7, which 
fetches the jars you need from remote servers. We just need to take 
these, sign them and they are ready to deploy.

The xml component uses this stuff, so is  Ant1.7 only. I'm tempted to 
make it Java1.5 only too, but that may be a bit too leading edge.

-steve


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl