Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted
 sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: NIO 2.0 == Ant 2.0? was Re: Java NIO support
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <4F3D5D39.1000603@callenish.com>
Date: Thu, 16 Feb 2012 23:36:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4F33356-4D08-4AD1-BB8B-CA4976961552@hibnet.org>
References: 
 <CAFvvX=a6iURwebprsUYDhtwcmNdwwbgr=88yfAiXpSuCOKFBuQ@mail.gmail.com>
 <87obtc1l08.fsf@v35516.1blu.de> <4F39559A.80003@callenish.com>
 <87haytzeoi.fsf@v35516.1blu.de> <4F3AAFD1.9050508@callenish.com>
 <0034F824-F1B4-4893-B835-65DC6226B4F7@hibnet.org>
 <4F3D5D39.1000603@callenish.com>
To: "Ant Developers List" <dev@ant.apache.org>


Le 16 f=E9vr. 2012 =E0 20:47, Bruce Atherton a =E9crit :

> I'd hope to go further than that in backwards compatibility. I work =
with a lot of companies that are:
>=20
>    a) resistant to learning new things unless there is a good reason =
for it (such as the migration from Apache HTTP Server from 1.x to 2.x to =
resolve security issues)
>=20
>    b) have a number of separate Ant build scripts that follow =
different standards in different areas of the company, particularly if =
they have
>=20
> and c) need to have a justification to allocate resources to upgrade =
and change a working build to use new features, which standardizing =
builds across the organization using new features in a major release =
that simplify the build system may offer them.

I don't know conclusion you're having there. Such companies shouldn't =
worry about any new major version, because they actually do want to =
stick with the old one for stability purpose. I guess that the companies =
which would be troubled is the ones which want to keep up with the =
releases, migrations from one version to another should not be too =
painful.

> You are right about the plugin parser architecture in Ant 1.x, but one =
of the problems with it is that there is nothing shipped by default. =
What I meant was that I would love it if Ant 2 also represented a point =
where new builds could think about using a new build format =
automatically, just based on file extension or a flag on the command =
line. That might encourage new projects to adopt it.

Well, again, I think it's already there, no need to wait for an Ant 2.0 =
:)
If you add the groovy-front.jar in Ant's boot classpath, write a =
build.groovy, then a launch of ant with no parameter on the command line =
will execute your groovy build script. See =
ProjectHelperRepository.getProjectHelperForBuildFile(Resource)

Nicolas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org