On 2020-09-13, Alan Snyder wrote:
> Given that I have installed an external ant task library in an appropriate
> location, I know of two ways to make the tasks accessible in a build script:
> 1. Add an xmlns attribute to some element, such as
>
> 2. Add a taskdef inline, such as
>
> T
On 2020-09-15, Dave Brosius wrote:
> I have an ant task using ant 1.10.8, that includes use of the
> task as such:
> **duplicate="preserve"*>
> includes="**/*" />
>
> ...
>
>
> There are in fact file collsions between the
If I have to include the xmlns attribute at each use of a task from the
library, then this is not what I want.
> On Sep 21, 2020, at 1:24 AM, Stefan Bodewig wrote:
>
> On 2020-09-13, Alan Snyder wrote:
>
>> Given that I have installed an external ant task library in an appropriate
>> location
On 9/21/20 4:32 AM, Stefan Bodewig wrote:
On 2020-09-15, Dave Brosius wrote:
I have an ant task using ant 1.10.8, that includes use of the
task as such:
...
There are in fact file collsions between the two jars.
W
On 2020-09-21, Alan Snyder wrote:
> If I have to include the xmlns attribute at each use of a task from the
> library, then this is not what I want.
Then either I don't understand what you want or you want something that
is not possible with XML namespaces :-)
XML namespaces care for URIs, not
I think you are understanding correctly.
It sounds like what I want might require either an include statement (textual
inclusion) or project inheritance.
> On Sep 21, 2020, at 9:58 AM, Stefan Bodewig wrote:
>
> On 2020-09-21, Alan Snyder wrote:
>
>> If I have to include the xmlns attribute at
On 2020-09-21, Alan Snyder wrote:
> I think you are understanding correctly.
> It sounds like what I want might require either an include statement (textual
> inclusion) or project inheritance.
If you wanted something like project inheritance, then the projects need
to be aware and use "their p
Hi Dave
On 2020-09-21, Dave Brosius wrote:
> In the end i just wrote my own custom ant task to do what jar was
> supposed to do. What i noticed was that one of the jars had
> 1) no entries for the directories themselves
> 2) items out of alphabetical order.
> Don't know if that confuse
