DO NOT REPLY [Bug 24592] New: - support @input for the exec task

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24596] New: - Problem using ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24596] - Problem using ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24592] - support @input for the exec task

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

AW: Namespace support in ant 1.6

>Von: peter reilly [mailto:[EMAIL PROTECTED] >Gesendet: Montag, 10. November 2003 19:21 >An: Ant Developers List >Betreff: Namespace support in ant 1.6 >Hi, >I would like to get some movement on the outstanding issues >of ant 1.6. +1 >One of the outstanding issues is what namespace to use >fo

Re: AW: Namespace support in ant 1.6

On Tuesday 11 November 2003 08:57, Antoine Levy-Lambert wrote: > >Von: peter reilly [mailto:[EMAIL PROTECTED] > >Gesendet: Montag, 10. November 2003 19:21 > >An: Ant Developers List > >Betreff: Namespace support in ant 1.6 > > > > > >Hi, > >I would like to get some movement on the outstanding issue

AW: AW: Namespace support in ant 1.6

Which of the 3 solutions you propose is the best in terms of preparing the transition to 1.7 and roles ? And the easiest to understand for users ? How can we formulate the rules in terms of when an xml prefix such as antcontrib: is required ? When is it optional ? On the details side, I did not

Re: Namespace support in ant 1.6

On Mon, 10 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > I would like to get some movement on the outstanding issues > if ant 1.6. This is appreciated a lot by me. Thanks for going ahead, I appologize for letting the ball drop - I've been too busy with real-life and real-life work. > One

ant-type attribute (was Re: antlibs/namespaces)

On Thu, 6 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > On Thursday 06 November 2003 10:02, Stefan Bodewig wrote: >> On Wed, 5 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: >> > well there is an undocumented attribute ant-type >> >> we really should document it. > Yes... > > Note that w

Re: antlibs/namespaces

On Thu, 6 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > One oddity is that the implementation of elements is now > exposed. Yes, I see you've "fixed" the specific case by now, but it remains a little strange. But then again it doesn't, as the version which uses addTask is open for polymor

Re: AW: AW: Namespace support in ant 1.6

On Tuesday 11 November 2003 09:33, Antoine Lévy-Lambert wrote: > Which of the 3 solutions you propose is the best in terms of preparing the > transition to 1.7 and roles ? The third. > > And the easiest to understand for users ? The first. (I think). The second for people that want to write xml syn

RE: Namespace support in ant 1.6

I'll just wade in here with my 2p. I agree that with the number of Ant based variants...maven, jelly etc... . and people embedding Ant inside their own applications that their is a need to avoid collision using namespacein addition this will also allow intermixing of Ant with other xml voca

Re: antlibs/namespaces

On Tuesday 11 November 2003 10:01, Stefan Bodewig wrote: > On Thu, 6 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > One oddity is that the implementation of elements is now > > exposed. > > Yes, I see you've "fixed" the specific case by now, but it The reason I fixed this is that in this c

cvs commit: ant/src/main/org/apache/tools/ant/taskdefs MacroDef.java

peterreilly2003/11/11 04:01:26 Modified:src/main/org/apache/tools/ant/taskdefs MacroDef.java Log: Implement the sequential element of macrodef by a createSequential and not a addTask() Revision ChangesPath 1.12 +72 -18ant/src/main/org/apache/tools/ant/taskdefs/

cvs commit: ant/src/main/org/apache/tools/ant/taskdefs MacroDef.java

peterreilly2003/11/11 04:02:09 Modified:src/main/org/apache/tools/ant/taskdefs Tag: ANT_16_BRANCH MacroDef.java Log: Sync with HEAD Revision ChangesPath No revision No revision 1.7.2.5 +72 -18ant/src/ma

[VOTE] macrodef - do attributes as properties or substitutions

Hi, I don't think that another discussion thread will lead us anywhere. Instead of trying to summarize what has been discussed, let me point to the archives (I hope the list is complete):

Re: [VOTE] macrodef - do attributes as properties or substitutions

On Tuesday 11 November 2003 12:22, Stefan Bodewig wrote: > Stefan > > OK, how do we want to implement attributes: > > [ ] as textual substitution > [X] as "real" Ant properties Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] F

RE: [VOTE] macrodef - do attributes as properties or substitution s

> OK, how do we want to implement attributes: [ ] as textual substitution [X] as "real" Ant properties Jan

AW: [VOTE] macrodef - do attributes as properties or substitutions

On Tuesday 11 November 2003 12:22, Stefan Bodewig wrote: > Stefan > > OK, how do we want to implement attributes: > > [ ] as textual substitution > [X] as "real" Ant properties Antoine - To unsubscribe, e-mail: [EMAIL PROTECTE

RE: Namespace support in ant 1.6

I think the right thing, technically, is to use (b), however due to the way conditions where defined (using class extension) and due to the fact that extends condition, this makes for a very ugly result. Is there a way to redefine antcontrib's to make it show a syntax like (c) eventhough is using

Re: Namespace support in ant 1.6

On Tue, 11 Nov 2003, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote: > Is there a way to redefine antcontrib's to make it show a > syntax like (c) eventhough is using (b) rules? Not as long as Ant doesn't typedef - and Ant can't do that unless we have a way to associate different classes with

Re: Namespace support in ant 1.6

On Tuesday 11 November 2003 14:39, Jose Alberto Fernandez wrote: > I think the right thing, technically, is to use (b), > however due to the way conditions where defined (using class extension) > and due to the fact that extends condition, this makes for a very > ugly result. Is there a way to red

Beta3?

I've started using Ant 1.6 beta1 for many things at work, but I cannot start forcing all projects to use it, 'cause I want to use namespaces and the Ant namespace name changed, but no beta has this change yet... So I'm feeling kind of stuck. I know active discussions are going on to try to get 1.6

Re: Namespace support in ant 1.6

On Tue, 11 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > The simplest way is to introduce roles. Sure - but then we are way out of Ant 1.6 land. At least if we take the released betas as an indication of what 1.6 was supposed to be. Stefan

Re: Beta3?

On Tue, 11 Nov 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > I'd really appreciate the release of a Beta3 in the mean time. IMHO we shouldn't increase confusion by releasing beta3 before we know what the details of 1.6-final are going to be. I'd very much prefer to get the few remaining

RE: Beta3?

> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > On Tue, 11 Nov 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > > I'd really appreciate the release of a Beta3 in the mean time. > > IMHO we shouldn't increase confusion by releasing beta3 before we know > what the details of 1.6-final

RE: [VOTE] macrodef - do attributes as properties or substitutions

OK, how do we want to implement attributes: [X] as textual substitution [ ] as "real" Ant properties I know I am not a committer, but ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTE

RE: [VOTE] macrodef - do attributes as properties or substitution s

> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > OK, how do we want to implement attributes: > > [X] as textual substitution > [ ] as "real" Ant properties - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

RE: [VOTE] macrodef - do attributes as properties or substitutions

I don't have a vote but if I did, I'd be [X] as textual substitution [ ] as "real" Ant properties -Original Message- From: Dominique Devienne [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 10:14 AM To: 'Ant Developers List' Subject: RE: [VOTE] macrodef - do attributes as pr

RE: Namespace support in ant 1.6

> From: peter reilly [mailto:[EMAIL PROTECTED] > > On Tuesday 11 November 2003 14:39, Jose Alberto Fernandez wrote: > > I think the right thing, technically, is to use (b), > > however due to the way conditions where defined (using class > > extension) and due to the fact that extends condition

[PATCH] to whatsnew for 1.6

I noticed that a change that I submitted (and then was accepted) was never added into the WHATSNEW file. (the addition of reallyquiet attribute to ). Attached is the patch to add that. -- Larry Index: WHATSNEW === RCS file: /home/cv

Re: Namespace support in ant 1.6

Regarding XML namespaces... Something else that would interest me is how namespaced attributes will be handled. IMHO they should be allowed and ignored. But will a task implementation have the ability to query them? Cheers, --knut "peter reilly" <[EMAIL PROTECTED]> wrote in message news:[EMAI

Re: Namespace support in ant 1.6

On Tuesday 11 November 2003 16:49, Knut Wannheden wrote: > Regarding XML namespaces... > > Something else that would interest me is how namespaced attributes will be > handled. IMHO they should be allowed and ignored. But will a task > implementation have the ability to query them? Opps, at the

RE: macrodef - do attributes as properties or substitutions

I think I need to justify some more what do I think the way I do about macrodef. I know the vote is already going, but I really want for people to understand my position. To me macrodefs are for writing all those tasks that I am too lazy, or they are too simple for me to need to go and write and m

RE: Namespace support in ant 1.6

>I know that these shortcommings would be mitigated by using NameSpaces, >but yet >I still want to be able to lump all my antlibs into the default >namespace and >use them without namespace stuff. which is why I suggested having an ant processor switch stating a) if namespace processing is on b

DO NOT REPLY [Bug 24231] - command-line option to signify no more options

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: macrodef - do attributes as properties or substitutions

Wouldn't you say, though, Jose, that does replace those uses of for which had too big a footprint for the job? -Original Message- From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 11:19 AM To: Ant Developers List Subject: RE: macrodef - do attrib

RE: macrodef - do attributes as properties or substitutions

> From: Steve Cohen [mailto:[EMAIL PROTECTED] > > Wouldn't you say, though, Jose, that does replace > those uses of for which had too big a > footprint for the job? > Oh, but of course. I do plan to use macrodef to replace things that I did with before. But the reason they were done wit

DO NOT REPLY [Bug 24627] New: - [patch] make to include directory path when complaining about it

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24627] - [patch] make to include directory path when complaining about it

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23314] - org.apache.tools.ant.taskdefs.XSTLProcess Standard Parameter

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu