Anthony Goubard wrote:
I think that the fact that antcall has its own property context is not new. Maybe it is not documented clearly,Hi,
Hi,
In any case I am starting to think about ant 1.7 and further.
Here are the points which spring to my mind :
1) local properties,
Here I'd like to point out to something strange I saw last month; properties are local if you use antcall but not with depends :
there should be some manual pages concerning the scope of properties and references.
1st remarks : I don't know why it's looking my tools.jar in jre/lib as it's
in jdk1.4/lib (on my jdk 1.4.2_01, Win 98 & Win ME, ANT 1.6.1)
Do not know either.
2nd remarks : As you can see the property is local, so there is a lot of confusion and I had some problems when I wanted to have a global variable. Do you consider this as a bug?
No for me this is a feature, which needs to be explained
Maybe it is possible to revive this vfs project. Other people sending emails to the list have mentioned the slide project
I first had to extend the VFS task as the copy task (for example) only takes one source or you need to specify one by one as nested element your files. I've added a setSrcdir(String sourceDir) and setIncludes(String fileList).
I also think that the project is on stand by as it seems that nobody is working on it at the moment. The last commits date from 11 months ago (except for a isHidden() method and a text correction in the license). I've discovered a few things (that I consider as bug) and submitted it (with the bug fix) to Adam Murdoch (the main programmer who did a very good job) but had no answer to them.
and also the new http://jcp.org/en/jsr/detail?id=170 Java Content Repository API proposal.
I have had a look at the JCR web page. I think that there is some overlap between VFS and JCR, but it is not the same.
I have the impression that JCR is meant for data storages which have versioning capabilities. It sounds like the equivalent of JDBC for
version control systems, a common API through which one could access CVS, Perforce, PVCS, Source Safe, Subversion,
but I do not feel like JCR is meant for accessing physical storages which do not have versioning capabilities such as file systems or jar/zip files.
About the dependencies note that if VFS depends on common logging and some others optional libraries depending on the file system : http://jakarta.apache.org/commons/sandbox/vfs/download.html
If you want to see what is the combination of ANT and VFS download my
software at
www.antcommander.com (note it's still under development but almost finished)
I think that the combination of VFS and ANT is great and it does not
necessary mean that ANT depends on VFS, the tasks can only use the VFS
library when they need it (with ftp, webdav, ...) such as some optional
tasks do now.
Sounds encouraging.
Maybe it is possible to find people to work on this agenda and revive the project.I especially like the todo list http://jakarta.apache.org/commons/sandbox/vfs/todo.html with # Add an equivalent of Ant path, fileset, dirset, filelist, etc. Ideally, these can be abstracted into a single data type. # Allow selectors, name mappers, and filters to be specified for the Ant tasks. # Add more selectors: XPath, Ant style, regular expression.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
