Here is an excerpt from my build script:
-- cut here --
-- cut here --
Depending upon the order of invocation of these targets, always
dumps the exact same value of ${bindings.wsdlLocation} in both the
targets.
The value, however, is diff
This helps me understand the background.
> > Lets say I'm a lazy programmer and dont want to
> > specify nested elements in my task for only one
> set
> > of
> > files that needs to be included. I'd rather
> provide
> > the option of specifying "includes" attribute as
> > well.
> > How do I do t
--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> > But does that mean I cannot have an
> > "includes" attribute on my task and need to rely
> upon
> > the explicit nested filesets only ?
>
> Yep, that's what I'd recommend.
>
> Is
> That much better than />?
>
> I personally don't think so.
--- Matt Benson <[EMAIL PROTECTED]> wrote:
> --- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> [SNIP]
> > Using an implicit fileset is just not as intuitive
> > as
> > using an explicit one, and I recommend you simply
> > derive
> > from Task, and have a
> > add(FileSet ds)
> > method. Your impl
I'm writing a custom task that require to support
"includes" attribute and nested fileset elements to
specify the location of source files. The source file
list should be a union of files specified in the
"includes" attribute and those specified in the nested
fileset element (is that a correct expe
