ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhatia Saurabh" <Bha...@OFAC.CH>
Subject RE: organizing 3rd party jars in the Ivy Repository
Date Thu, 05 Jul 2007 09:46:51 GMT
Thanks Xavier.

If my directory structure is /eclipse/birt/core/<revision>/core.jar.
How can I express this in my info element for this 3rd party dependency ?

e.g is this valid in the info element ?

<ivy-module version="1.0">
 <info organisation="eclipse" module="birt/core" revision="xxx"/>
	<artifact name="core" type="jar"/>
    <manager name="ofac-cm" org="ofac"/>
    <manager name="latest-revision" org="(?!ofac).*"/>

Or am I obliged to change my directory structure to: /eclipse/birt/<revision> to have
the following info element ?
<info organisation="eclipse" module="birt" revision="xxx"/>

It seems the path "sans revision" is confined to organisation and module ie just 2 attributes?.
Cant I express long namespaces like--
In my <info> element ?

Many thanks for taking the time.

-----Message d'origine-----
De : Xavier Hanin [] 
Envoyé : jeudi, 5. juillet 2007 11:28
À :
Objet : Re: organizing 3rd party jars in the Ivy Repository

On 7/5/07, Bhatia Saurabh <> wrote:
> What is the best way to organized 3rd party jars in the repository?
> Our war projects have 3rd party jars in their /WEB-INF/lib which which
> are currently not in the Ivy repository.
> Moreover, most of these jars have empty manifests too so I am wondering
> how I should go about adding them to the repository.
> For example, birt-oda.jar is most probably from eclipse/ibm.
> So should I create a structure like: /ibm/birt-oda/jars/birt-oda.jar
> With an ivy file that goes into: /ibm/birt-oda/ivys/ivy.xml
> Or should it be : /eclipse/..../ibm/eclipse/....

I suggest guessing the module name from the package used by the classes in
the jar. But this is only an idea, the more important is for users to get
comfortable with the name.

If I cant figure out the version from the manifest since there is none
> mentioned, should I leave the revision element blank in the ivy file ?

No, you should never leave the revision blank in a module in a repository.
If you don't know the revision at all, maybe you know where the jar
originally came from, if it's from acme foo 1.3, then the revision could be
acme-foo-1.3. If you really don't know, you can use the date, like 20070705
for instance. Having a version is very important because you never know if a
new version can come up in the future. So it's much better to always have a
unique revision.



Xavier Hanin - Independent Java Consultant

View raw message