Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (nike.apache.org: domain of jeanlouis.boudart@gmail.com
 designates 209.85.210.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPohPd=tVxG32Fk_4Cq_dZVvhF0kRC=aRQXvL4rX7c-yf_Urtw@mail.gmail.com>
References: 
 <CA+e2WO6oVtnyh+A81Ayoq9ixn7ADEG3_SX=RCRQps_k-iH8zfw@mail.gmail.com>
	<CA+e2WO7HdvWEY6sibg8Kmr+UnC32h+kpP1EDZxojXo90OBZ4eA@mail.gmail.com>
	<CA+e2WO5snAmd89553Fh0Qo4kJYgPwN4=gpNJoKd7SXvOgQ8YXw@mail.gmail.com>
	<B1D1B4AF-A533-4AF4-931B-247FBFA7BAF6@gmx.de>
	<CA+e2WO5EyOTp3q7eunKTbGZJrXGM_LRnDV27Xvn7R1Eqd7n8TA@mail.gmail.com>
	<1113156728826451397@unknownmsgid>
	<003f01ce47e1$c7eec210$57cc4630$@de>
	<4BD43543-5241-4FD0-9D70-E2F57532FD09@gmx.de>
	<CAPohPd=tVxG32Fk_4Cq_dZVvhF0kRC=aRQXvL4rX7c-yf_Urtw@mail.gmail.com>
Date: Thu, 9 May 2013 17:43:50 +0200
Message-ID: 
 <CA+e2WO5OhAa_tPEA0-FrBKRhAHofhg2eF0H45BHsFO_LZfL5Gw@mail.gmail.com>
Subject: Re: Adding if/unless conditions on commandline args
From: Jean-Louis Boudart <jeanlouis.boudart@gmail.com>
To: Ant Developers List <dev@ant.apache.org>
Content-Type: multipart/alternative; boundary=047d7b4145d4b5526a04dc4aeaee

--047d7b4145d4b5526a04dc4aeaee
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 solved
isn't it ?


2013/5/6 Peter Reilly <peter.kitt.reilly@gmail.com>

> wow, I had forgot about that!
>
> Peter
>
>
> On Mon, May 6, 2013 at 12:55 AM, Antoine Levy Lambert <antoine@gmx.de
> >wrote:
>
> > Hi,
> >
> > I have committed a patch created by Peter Reilly back in 2007.
> >
> > The bugzilla PR is 43362 [1]
> >
> > If the community is happy with this change we will be able to close a
> > number of bug reports requesting if/unless on various elements .
> > For instance 49136 requesting if/unless support for attribute nested
> > element of manifest task,
> > 49036 add 'unless' attribute to JUnit test element,
> > ...
> >
> > Regards,
> >
> > Antoine
> >
> > [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=3D43362
> >
> > On May 3, 2013, at 5:37 AM, Jan Mat=E8rne (jhm) wrote:
> >
> > > AFAIK this was discussed several times in the past (few years) with t=
he
> > > result, that having if/unless an _all_ elements would decrease
> > > maintainability of the build scripts.
> > >
> > > But +1 from me for having if/unless on nested elements.
> > >
> > > What about supporting more complex conditions via nested <condition>
> > > elements?
> > >
> > >
> > > Jan
> > >
> > >> -----Urspr=FCngliche Nachricht-----
> > >> Von: Michael Clarke [mailto:michael.m.clarke@gmail.com]
> > >> Gesendet: Freitag, 3. Mai 2013 11:01
> > >> An: Ant Developers List
> > >> Betreff: Re: Adding if/unless conditions on commandline args
> > >>
> > >> +1 from me too
> > >>
> > >> On 3 May 2013, at 09:37, Jean-Louis Boudart
> > >> <jeanlouis.boudart@gmail.com> wrote:
> > >>
> > >>> +1
> > >>>
> > >>>
> > >>> 2013/5/3 Antoine Levy Lambert <antoine@gmx.de>
> > >>>
> > >>>> I wonder whether we could not add if an unless on all nested
> > >> elements
> > >>>> in the framework ?
> > >>>>
> > >>>>
> > >>>> Regards,
> > >>>>
> > >>>> Antoine
> > >>>> On May 3, 2013, at 2:57 AM, Jean-Louis Boudart wrote:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> It's currently difficult to make reusable script when using <exec=
>
> > >>>>> task
> > >>>> or
> > >>>>> any other task using commandline args.
> > >>>>> We oftenly need some "dynamic arguments" and this can be
> > >> complicated.
> > >>>>>
> > >>>>> Therefor, i suggest to introduce if/unless conditions on comand
> > >> line
> > >>>> args :
> > >>>>>
> > >>>>> <exec executable=3D"git">
> > >>>>> <arg value=3D"commit"/>
> > >>>>> <arg line=3D"-a" if=3D"${commit.all.files}"/>  <arg value=3D"-m"/=
>  <arg
> > >>>>> value=3D"${commit.message}"/> </exec>
> > >>>>>
> > >>>>> I have a working implementation  with related tests and
> > >> documentation.
> > >>>>> Commandline.Arg class now extends ProjectComponent, and expose
> > >>>>> accessors for if/unless condition, and rely on PropertyHelper to
> > >> check conditions.
> > >>>>>
> > >>>>> Is this sufficient ? From what i have seen, it doesn't break
> > >>>>> backward compatibility at least all tests are green :p.
> > >>>>>
> > >>>>> The setProject(Project p) method should be invoked "automatically=
"
> > >>>>> by ProjectHelper isn't it ?
> > >>>>>
> > >>>>> If ant is used in pure java and we ommited invoking
> > >>>>> setProject(Project p) method, it should also works as
> > >> PropertyHelper seems null safe.
> > >>>>>
> > >>>>> If there is no objection i will commit this this week end.
> > >>>>
> > >>>>
> > >>>> ------------------------------------------------------------------=
--
> > >> -
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For
> > >> additional
> > >>>> commands, e-mail: dev-help@ant.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Jean Louis Boudart
> > >>> Independent consultant
> > >>> Apache EasyAnt commiter http://ant.apache.org/easyant/
> > >>
> > >> --------------------------------------------------------------------=
-
> > >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additiona=
l
> > >> commands, e-mail: dev-help@ant.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> >
> >
>


--=20
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/

--047d7b4145d4b5526a04dc4aeaee--