ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Buck" <>
Subject public repositories: what is best practice for, how do you do, ...
Date Wed, 22 Nov 2006 12:51:51 GMT
I set up my own public repository. It works great, but until now I have
only dealt with very simple content and structures (one directory and
single jars).
In general, what is the best way to handle declaring publications and
declaring dependencies, when there exists several jars, in some
subdirectory, jars not named after the product.
For instance:
|  |---commons
|  |   |---util
|  |       |---1.0.1
|  |           |---lib (ws-commons-util-1.0.1.jar)
|  |---xmlrpc
|       |---3.0
|           |---lib (many jars)
    |---2.8.1  (resolver.jar, xercesImpl.jar, xml-apis.jar)

I have two questions...

1. When I try to resolve the third party product, xerces-j, Ivy
indicates that it is trying to resolve jars named xerces-j.jar! But,

<ivy-module version="1.0">
  <info organisation="apache" module="xerces-j" revision="2.8.1"
status="release" publication="20060914060200">
    <license name="Apache"
    <ivyauthor name="VeriSign" url=""/>
    <repository name="ivyrep" url="http://localhost:20080/ivyrep/"
pattern="[organisation]/[module]/ivy-[revision].xml" ivys="true"
    <description homepage="">Xerces2
Java is a high performance, fully compliant XML
    <conf name="default" description="for minimal use"/>
    <artifact name="xercesImpl" type="jar" conf="default"/>

Declares that xercesImpl.jar is the publication.

2. It turns out that xmlrpc depends upon ws-commons-util, and each of
these products as provided by apache stores the jars in a lib directory.
I would like to preserve the directory structure as provided by the
vendor, in this case Apache (keep the jars in the lib directory). How do
you declare publications in this case, and declare dependencies? I have
not been able to get this to work. In a nutshell, I'd like to be able to
declare a publication in a respository by indicating a subdirectory to
look in, and the regular expression pattern for the specific jar files
to match.

3. In general, I'd like to be able to declare different classes of
publications in the public repository: doc, jars, all. Have 'docs' so
developers can download doc on demand only. Have 'jars' so the product
may be compiled. Have 'all' so we can bring down a full product which
may be comprised of shell scripts, jars, docs, and the like.


View raw message