Hi Brian. Annoyingly you'll have to end up with N lots of ivy.xml files :(
You can define a filesystem resolver with its own name template, so the ivy file for the fombinator project from chumbley.org could be chumbley.org/fombinator-1.2.6-ivy.xml. I did this on a project and it's surprisingly quick (we rolled a little script to generate default ivy.xml files). Cheers, Dan 2008/6/19 Brian Matzon <[EMAIL PROTECTED]>: > Hi All > > I must be missing something basic... I am trying to publish some 3rd party > jars into our repository. These are not available in any maven repo, so I > cannot use the install target I have been using so far. > > I think I can solve it by creating an ivy.xml file with no dependencies and > the relevant artifact - the problem is that I need to publish several jars, > and that would require me to have N ivy.xml files :( > > It is not an option to use the url attribute of the artifact tag, since > they are not available elsewhere. They must be placed into - versioned - > into the repo for later access. > > -- > Brian Matzon > Certus > >
