> From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
>
> Dominique : can you use a patched version of ant 1.6.0 until we provide
> an official new release ?
Actually, thanks to Peter's answer I'm not stuck any more.
At first I thought I couldn't use namespaces at all to turn around
the bug, whi
Stefan Bodewig wrote:
On Tue, 06 Jan 2004, Antoine Lévy-Lambert <[EMAIL PROTECTED]>
wrote:
Dominique Devienne wrote:
Does this warrant a 1.6.1? I'm actually quite stuck because of this
bug
This bug is impacting the most salient feature of ant 1.6.0, in the
core of ant, so it is i
On Tue, 06 Jan 2004, Antoine Lévy-Lambert <[EMAIL PROTECTED]>
wrote:
> Dominique Devienne wrote:
>
>>Does this warrant a 1.6.1? I'm actually quite stuck because of this
>>bug
>>
>>
> This bug is impacting the most salient feature of ant 1.6.0, in the
> core of ant, so it is important.
+1
> D
Dominique Devienne wrote:
Does this warrant a 1.6.1? I'm actually quite stuck because of this bug
This bug is impacting the most salient feature of ant 1.6.0, in the core
of ant, so it is
important.
Do we want to fix other bugs in 1.6.1 ?
What do you think ?
Dominique : can you use a patc
The easiest fix until 1.6.1 is to remove the antlib:org.apache.tools.ant
declarations.
Peter
Dominique Devienne wrote:
Does this warrant a 1.6.1? I'm actually quite stuck because of this bug
I've been making extensive use of namespaces in my builds based on beta1!
--DD
-Original Messag
Does this warrant a 1.6.1? I'm actually quite stuck because of this bug
I've been making extensive use of namespaces in my builds based on beta1!
--DD
> -Original Message-
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
> Thanks for the report.
> Yes, the handling of the ant namesp
Thanks for the report.
Yes, the handling of the ant namespace is incorrect due
to a change between 1.6beta3 and 1.6.0.
I have placed a fix now.
Peter
Dominique Devienne wrote:
Just starting updating from Ant 1.6 beta1 to 1.6 official,
and I've having a bad surprise. It seems there's a problem
handl
Just starting updating from Ant 1.6 beta1 to 1.6 official,
and I've having a bad surprise. It seems there's a problem
handling the default Ant namespace when explicitly specified,
or when used as the default namespace, at least for the
task.
Have I doing something wrong??? --DD
P:\com_lgc\10.0.7
On Monday 05 May 2003 20:20, J.Pietschmann wrote:
> peter reilly wrote:
> > I would agree with most of what Nicola says. I think
> > that XML ns is a "heavy" solution for name clashing
> > of names defined in a antlib. Moreover I do not
> > think that the antlib needs to define a qualified name.
>
peter reilly wrote:
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be used - even with the
peter reilly wrote, On 04/05/2003 2.03:
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be
>
> Costin Manolache wrote, On 03/05/2003 8.22:
> ...
> > One use case I had in mind for CH was a namespace like "jmx:...",
> > where the JMXComponentHelper would use the JMX metadata to
> create the
> > task ( no ant table ). That's clearly outside the scope of
> antlib or ant (
> > it's just
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be used - even with the current command.
Costin Manolache wrote, On 03/05/2003 16.14:
Nicola Ken Barozzi wrote:
...
I think that XML namespaces really make things much more difficult to
write and understand. One thing I don't like in Jelly is just this use
of namespaces, where all scripts seem cluttered and simply difficult to
read.
I ag
Nicola Ken Barozzi wrote:
This seems interestig, and brings up what XML namespaces can be used for.
XML namespaces are indented to disambiguate short local element
and attribute names. Any sematic associated to XML namespaces
beside this has to be weighted carefully.
Lets take an example. There are
Nicola Ken Barozzi wrote:
>
> Costin Manolache wrote, On 03/05/2003 8.22:
> ...
>> One use case I had in mind for CH was a namespace like "jmx:...",
>> where the JMXComponentHelper would use the JMX metadata to create the
>> task ( no ant table ). That's clearly outside the scope of antlib or ant
Costin Manolache wrote, On 03/05/2003 8.22:
...
One use case I had in mind for CH was a namespace like "jmx:...",
where the JMXComponentHelper would use the JMX metadata to create the
task ( no ant table ). That's clearly outside the scope of antlib or ant (
it's just a custom task ).
This seems i
17 matches
Mail list logo
