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.
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
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
Ich kehre zurück am 13.05.2013.
In dringenden Fällen, kontaktieren Sie bitte
ErwinpunktTrataratgebitpunktde oder
TompunktKraussatgebitpunktde.
Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht Re:
Evaluating Bintray as a distribution platform for easyant plugins gesendet
am
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
