Re: Adding if/unless conditions on commandline args

2013-05-09 Thread Antoine Levy-Lambert
Hi, I also figured out that if and unless prefix are not going to mask potential if or unless attributes already existing in custom types or data types. I was glad to see that the patch was still usable with little manual work after so many years in Bugzilla. I did not try to create an implement

AUTO: Carsten Pfeiffer ist außer Haus (Rückkehr am 13.05.2013)

2013-05-09 Thread Carsten . Pfeiffer
Ich kehre zurück am 13.05.2013. In dringenden Fällen, kontaktieren Sie bitte ErwinTratargebitde oder TomKraussgebitde. Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "Re: Evaluating Bintray as a distribution platform for easyant plugins" gesendet am 09.05.2013 17:33:52. Diese

Re: Adding if/unless conditions on commandline args

2013-05-09 Thread Peter Reilly
The problem of not using namespaces is that they would not be backward compatible. Also the attributes are 'magic' and we already have 'id' as a magic attribute, which makes task code hard to reason about. Peter p.s, I really hate xml namespaces! On Thu, May 9, 2013 at 4:43 PM, Jean-Louis Boudar

Re: Adding if/unless conditions on commandline args

2013-05-09 Thread Jean-Louis Boudart
I'm not a big fan of adding this feature through internal namespaces, was there any complication to do it without namespaces ? Anyway it does the job, and stuff looks extensible so i'm fine with current solution if no one objects. 49036 add 'unless' attribute to JUnit test element was already sol

Re: Evaluating Bintray as a distribution platform for easyant plugins

2013-05-09 Thread Jean-Louis Boudart
Let's first define a few things. We need to distribute many things : - easyant distribution itself (shipping ivy, ant and easyant-core.jar itself). As the entry point of easyant it remains "natural" to be distributed through dist.apache.org - additionnal task we may write in future.