On Fri, 4 Apr 2003, Jose Alberto Fernandez [EMAIL PROTECTED]
wrote:
I would like for ANT to do this for me, transparently.
property name=fileurl locationURL=${myfile}/
or somethig like that.
Sure, should be trivial using FileUtils#toURI together with
setLocationURL(File), I'm just
: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: 07 April 2003 08:38
To: [EMAIL PROTECTED]
Subject: Re: Using files in classpath in task file=
On Fri, 4 Apr 2003, Jose Alberto Fernandez [EMAIL PROTECTED]
wrote:
I would like for ANT to do this for me, transparently.
property name
Nicola Ken Barozzi wrote, On 07/04/2003 9.11:
...
After the replies and a bit of thought, maybe even setXYZUrl(URL) is not
the right solution.
We have a FTP task, a get task, etc... putting the URL as a parameter
short-circuits the process of getting stuff and using it, and
potentially makes
Stefan Bodewig wrote, On 03/04/2003 8.17:
On Wed, 02 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
If I had it in jars I could ship it automatically with the jar that
has the task that generated index.xml, so I can easily do something
like:
xslt in=index.xml out=index.html
On Fri, 04 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
What I mean is not to change the passing of a File object. I mean
that we can *wrap* an URL in a File. So we pass a File, and use an
URL, getting a Virtual File System.
How so - put the URI into the name and abuse File as a
, making Ant use URLs instead of File in many tasks
would be a major backward-incompatible undertaking. --DD
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 9:22 AM
To: [EMAIL PROTECTED]
Subject: Re: Using files in classpath in task file
On Fri, 04 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
Sure. Look at the JDK 1.4 version,
Ahh, far to modern for Ant.
Because a URI can be navigated, and it's possible to make a File
from a URI.
Not always.
org.apache.tools.vfs.File extends java.io.File
But this version
Stefan Bodewig wrote, On 04/04/2003 17.55:
On Fri, 04 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
...
Because a URI can be navigated, and it's possible to make a File
from a URI.
Not always.
Agreed, not always with the same features. Listing files in a http URL
dir is not usually
Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: 03 April 2003 07:18
To: [EMAIL PROTECTED]
Subject: Re: Using files in classpath in task file=
On Wed, 02 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
If I had it in jars I could ship it automatically with the jar
Stefan Bodewig wrote:
org.apache.tools.vfs.File extends java.io.File
But this version cannot be the argument for the (existing) setters.
For this to work, IntrospectionHelper will need to take special care
(i.e. if setXYZ(java.io.File) is found, actually pass it an instance
of
On Wed, 02 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
If I had it in jars I could ship it automatically with the jar that
has the task that generated index.xml, so I can easily do something
like:
xslt in=index.xml out=index.html
style=resource:/a/style.xsl/
I see.
A common usage of xslt is to postprocess xml results for documentation,
like in junit, jdepend, etc. The problem is that AFAIK the xslt task
needs a file, not an URL, and hence not a jar resource.
All tasks that resolve files IIUC call
public File resolveFile(File file, String filename)
in
On Wed, 02 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
The problem is that AFAIK the xslt task needs a file, not an URL,
and hence not a jar resource.
Errm, where does it need the file?
All tasks that resolve files IIUC call
public File resolveFile(File file, String filename)
Stefan Bodewig wrote, On 02/04/2003 17.34:
On Wed, 02 Apr 2003, Nicola Ken Barozzi [EMAIL PROTECTED] wrote:
The problem is that AFAIK the xslt task needs a file, not an URL,
and hence not a jar resource.
Errm, where does it need the file?
Sorry, I'm not clear.
Code:
xslt in=index.xml
14 matches
Mail list logo
