Dominique Devienne-2 wrote:
>
> My mistake. You must use comma indeed, instead of semi-colon.
>
> The 'includes' attribute of *does* accept of comma-separated
> list of patterns (make sure to use forward slashes, even on windows),
> which *must* be relative to the fileset's dir attribute. You
On 11/5/07, MikeO <[EMAIL PROTECTED]> wrote:
> I tried something similar before, but from my experience, it seems that the
> fileset task doesn't like dealing with semi-colon separated lists, and only
> deals with single files/directories.
My mistake. You must use comma indeed, instead of semi-col
This doesn't seem to be working for me. I am printing out the classpath
(using ant-contrib) with this code after the path task:
Your classpath: ${printPath}
and it displays nothing.
I tried something similar before, but from my experience, it seems that the
fileset task doesn't like dealing w
On 11/2/07, MikeO <[EMAIL PROTECTED]> wrote:
> classpath.jar.include=lib;lib\ext;lib\config
> What am I doing wrong? Am I even on the right track? Thanks in advance.
You're better off leveraging the includes attribute of fileset in this
case IMHO.
env.properties
classpath.jar.include =
