Or you can consolidate the include when it's that
simple:
-Matt
--- jason heddings <[EMAIL PROTECTED]> wrote:
> Perfect... Thanks. (And so simple!)
>
>
> -Original Message-
> From: Burgess, Benjamin
> [mailto:[EMAIL PROTECTED]
> Sent: Friday, 08 September, 2006 10:54
> To: Ant Us
Perfect... Thanks. (And so simple!)
-Original Message-
From: Burgess, Benjamin [mailto:[EMAIL PROTECTED]
Sent: Friday, 08 September, 2006 10:54
To: Ant Users List
Subject: RE: DirSet Top-Level Dirs Only
Should be:
Something like that at least.
Ben
-Original Message
if your interfaces follow some kind of a naming pattern
("IInterfaceName.java"), you can select them all using a fileset with a
nested include
/t
>-Original Message-
>From: Bret Kumler [mailto:[EMAIL PROTECTED]
>Sent: Friday, September 08, 2006 4:42
Should be:
Something like that at least.
Ben
-Original Message-
From: jason heddings [mailto:[EMAIL PROTECTED]
Sent: Friday, September 08, 2006 12:53 PM
To: 'Ant Users List'
Subject: DirSet Top-Level Dirs Only
I'm trying to craft a dirset that contains only the topl-evel
di
I'm trying to craft a dirset that contains only the topl-evel directories of
the supplied path... I took this approach:
But that doesn't seem to quite work. Effectively, I want to have all the
first-level children of the ${basedir} directory only. Ideally, not even
${basedir} would be r
You have got to set the location and the target attributes of
the import task, in ant 1.7 there is a utility method bindToTask
to do this.
task = project.createTask("import");
task.bindToOwner(self);
task.setFile("import.me.xml");
task.execute();
However, you are using beanshell,
Sorry, I forgot to mention one thing, when I sync to source sometimes
there's new interfaces.
These interfaces end up missing in the instrumented classes.
I'm trying to avoid adding a new for each interface.
-Original Message-
From: Chun Ji [mailto:[EMAIL PROTECTED]
Sent: Thursday, Sep
(I couldn't find anything in the mail-archives, nor on google, on this,
so I'm asking here. It's my first post to this list and I haven't
subscribed it previously either.)
Hi all,
Short version: How to use from a custom task?
Long version:
I'm trying to make a custom import task that perfo
Hi,
I'm faced with the following situation:
- The stylesheet parameters supposed to be passed to the XSLT processor
should be configurable from the "outside world", like this
- I want to provide a macro that creates a bunch of elements
with name and expression attributes based on the numb
