On Tuesday 18 November 2003 14:27, Christopher Lenz wrote:
> peter reilly wrote:
> > On Monday 17 November 2003 17:20, Dominique Devienne wrote:
> >>Slightly related, if I extracted or wrote a schema for Ant,
> >>and specified an xsi:schemaLocation attribute in ,
> >>will Ant ignore the attribute,
peter reilly wrote:
On Monday 17 November 2003 17:20, Dominique Devienne wrote:
Slightly related, if I extracted or wrote a schema for Ant,
and specified an xsi:schemaLocation attribute in ,
will Ant ignore the attribute, or barf?
If the class did not contain a setSchemaLocation() method or
was an
On Mon, 17 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote:
> We could modify namespace processing to ignore attributes not in the
> "right" namespace.
+1
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
Dominique Devienne wrote:
From: Christopher Lenz [mailto:[EMAIL PROTECTED]
Dominique Devienne wrote:
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for and does not matter?
Conceptually they are part of the Ant XML dialect to me,
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]
> Dominique Devienne wrote:
> >>From: peter reilly [mailto:[EMAIL PROTECTED]
> >>
> >>>On Monday 17 November 2003 17:01, Dominique Devienne wrote:
> >>>
> >>>So the NS for and does not matter?
> >>>Conceptually they are part of the Ant XML dialec
Dominique Devienne wrote:
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for and does not matter?
Conceptually they are part of the Ant XML dialect to me,
so seeing them in no namespace at all seems weird??? --DD
If no namespace
On Monday 17 November 2003 17:20, Dominique Devienne wrote:
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> >
> > > On Monday 17 November 2003 17:01, Dominique Devienne wrote:
> > >
> > > So the NS for and does not matter?
> > > Conceptually they are part of the Ant XML dialect to me,
> > > so
> From: peter reilly [mailto:[EMAIL PROTECTED]
> > On Monday 17 November 2003 17:01, Dominique Devienne wrote:
> >
> > So the NS for and does not matter?
> > Conceptually they are part of the Ant XML dialect to me,
> > so seeing them in no namespace at all seems weird??? --DD
>
> If no namespace
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> >
> > Yes, this is std xml (not visible from ant processing code):
> >
> > > xmlns:ant="antlib:org.apache.tools.ant"
> > xmlns:acme="antlib:org.acme.anttasks">
> >
>
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> Yes, this is std xml (not visible from ant processing code):
>
> xmlns:ant="antlib:org.apache.tools.ant"
> xmlns:acme="antlib:org.acme.anttasks">
>
>
>
>
>
>
>
>
Thanks to Peter and Chris. Option B looks good to me
as well... this can also be called beta1 behavior,
which is less error-prone/confusing with macrodef
elements, for one thing. Incidentally I'd probably
use the first example more often than not.
-Matt
--- Christopher Lenz <[EMAIL PROTECTED]>
Matt Benson wrote:
--- peter reilly <[EMAIL PROTECTED]> wrote:
For example:
The arguments are equal
Okay, how about redoing the same example with:
...
or will that syntax be available at all?
That should be:
On Monday 17 November 2003 16:11, Matt Benson wrote:
> --- peter reilly <[EMAIL PROTECTED]> wrote:
> > For example:
> >
> > > xmlns:acme="antlib:org.acme.anttasks">
> >
> >
> >
> >
> >
> >
> >
> >The arguments are equal
--- peter reilly <[EMAIL PROTECTED]> wrote:
>
> For example:
>
> xmlns:acme="antlib:org.acme.anttasks">
>
>
>
>
>
>
>
>The arguments are equal
>
>
>
>
>
Okay, how about redoing the same example w
On Mon, 17 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote:
> From the feedback, I think that we should implement option b),
+1
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECT
Last week, I sent a questionary about
namespace support in ant 1.6.
http://marc.theaimsgroup.com/?l=ant-dev&m=106848848930806&w=2
>From the feedback, I think that we should
implement option b), nested elements of tasks/types
have the same namespace uri as the containing task/type,
unless they are
16 matches
Mail list logo