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 (nike.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 v1081)
Subject: Re: Publishing non-jar artifacts
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <4C72FA90.9070401@palantir.com>
Date: Tue, 24 Aug 2010 11:03:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8F00CEB-A54B-4D72-98ED-C7C44F519F6D@hibnet.org>
References: <4C65E1E4.9040209@palantir.com>
 <AANLkTin80Lx-KEeGgZf=y_LF9+mM54S+ztJ2oJ5u2hai@mail.gmail.com>
 <4C6C85A2.7010704@palantir.com>
 <A4432ACD-C23A-41A1-A75C-CFE9D06E7516@hibnet.org>
 <4C72FA90.9070401@palantir.com>
To: "Ant Developers List" <dev@ant.apache.org>


Le 24 ao=FBt 2010 =E0 00:47, Carl Myers a =E9crit :

> The "common and reusable" pattern is "I have a mess of files".  Why =
does it need to be more specific?
>=20
> Some examples:
>=20
> 1. Our custom build system consists of several xml and properties =
files.  We would like to version our build system itself so that just a =
small ant script is used to pull the build system, then it is used to =
perform the rest of the build.  We would like to have the build system =
cached, then extracted to a certain location, after an ivy resolve, but =
this must work within the eclipse workflow and the CLI workflow (but, I =
suppose, either way it will be the dev. running an ant script probably, =
so maybe IvyDE doesn't need to support it explicitly)

quite off topic, but this is amazingly exactly what I want to put in =
place for my projects. I think Easyant can help with that, but it is not =
yet there, so my recent long mail on easyant dev mailing list.

>=20
> 2. Sql files, or other generated artifacts that are not Jars.  I have =
a directory full of Sql files that several packages need to depend upon. =
What I really want to do is "build" these sql files (run tests, validate =
them), then publish them using ivy.  But when other things depend on =
them, they need the files in a certain location, not on their classpath. =
 I want to be able to use a construct where I say "resolve this package =
and place its contents here".
>=20
> 3. Configuration only packages.  This makes sense once your codebase =
gets big enough - and similar to #2 above, you want to have a bunch of =
xml or properties files or whatever and you want them to end up in a =
location on disk, not in the ether.
>=20
> I think this is a very general (and useful) case for Ivy to solve.

So you need IvyDE to launch a resolve of some ivy.xml file, and then =
retrieve the appropriate files in some defined place. IvyDE can already =
do that:
=
http://ant.apache.org/ivy/ivyde/history/latest-milestone/cpc/retrieve.html=


As I wrote, it is tied to the Java nature of a project, and an IvyDE =
classpath container has to exist even if you don't use it. It should be =
useable though.

But for IvyDE 2.2, I have just implemented a retrieve mechanism for non =
java project. So you would be able to right click on a project, select =
the Ivy menu and then select "Retrieve 'sql files'". And with Clint =
Burghduff patch I integrated too, the files get properly refreshed in =
Eclipse. I wouldn't consider the 2.2 as production ready, but an early =
feedback on that would be appreciated.

Nicolas


>=20
> -Carl
>=20
> On 08/19/2010 01:00 PM, Nicolas Lalev=E9e wrote:
>> pe, Ivy doesn't care. I have been able to make Ivy manage =
dependencies between flex projects. IvyDE on his side is mainly intended =
to be used in a Java projects (probably too tied to Java,
>=20
> --=20
> Carl Myers
> Palantir Technologies | Internal Tools Software Engineer
> cmyers@palantir.com
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20


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