Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@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 v1081)
Subject: Re: Jar file type naming conventions?
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: 
 <FF452E17060D614D89BF7FD3A07A88334FAEDA95A7@GVW1115EXC.americas.hpqcorp.net>
Date: Tue, 17 Aug 2010 16:14:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDB2C0B0-4DCE-4629-8956-2FB55C969B21@hibnet.org>
References: 
 <FF452E17060D614D89BF7FD3A07A88334FAEDA95A7@GVW1115EXC.americas.hpqcorp.net>
To: ivy-user@ant.apache.org


Le 16 ao=FBt 2010 =E0 19:21, Bailey, Darragh a =E9crit :

>=20
>=20
> Could someone point me towards where the jar file naming conventions =
that ivy and ivyde use are laid out?
>=20
> i.e. as what is described in the ivyde documentation for the source =
and javadoc types and suffixes.
> =
http://ant.apache.org/ivy/ivyde/history/latest-milestone/cpc/workspace.htm=
l
>=20
>=20
> I'm assuming that there is some standard convention mentioned =
somewhere and it's not just an arbitrary de facto convention?

This topic should deserve a page in the doc, you're right.

IvyDE will resolve the dependencies and artifacts you are requiring. =
Then with the pool of resolved artifacts, it has to decide which is a =
binary jar, which contains sources, and which contains javadocs.
For the binaries jars, it is relying on the "Accepted types": if the =
artifact has a type listed here, it is then added to the classpath.
For the sources, it is relying on the "Sources types".
For the javadocs, it is relying on the "Javadocs types".

The second step is to bind a source artifact with a binary one.
First if a binary jar has the same artifact name than a source one, =
there are bind together.
If none matched, then IvyDE search for sources which have one of the =
suffix specified in "Sources suffixes".
For instance, searching for the sources of mylib.jar (type=3Djar), IvyDE =
will look to bind it to the first one existing of:
* mylib.jar (type=3Dsource)
* mylib-source.jar (type=3Dsource)
* mylib-sources.jar (type=3Dsource)
* mylib-src.jar (type=3Dsource)

Note that IvyDE don't care about the extension, it can be .zip too.

Same apply for javadocs with respectively "Javadocs suffixes".

It is enough clear, I'll probably use what I just wrote as the doc :)

Nicolas