ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brown, Carlton" <>
Subject RE: How to use Ivy to publish artifacts to archiva or arifactory?
Date Mon, 05 May 2008 13:32:38 GMT
> -----Original Message-----
> From: Jing Xue [] 
> Sent: Saturday, May 03, 2008 9:58 AM
> To:
> Subject: Re: How to use Ivy to publish artifacts to archiva 
> or arifactory?
> On Sat, May 03, 2008 at 12:07:28PM +0200, Lasse Knudsen wrote:
> > With actual path do you mean like 
> G:\Archiva\data\repositories\internal\? 
> > I tried that with sftp and filesystem.
> Yes. In general, it needs to be whatever target path you 
> would use when you manually perform the file copy operation.
> > With the filesystem it seems to
> > work fine but archiva do not get it correctly. First the 
> published jar 
> > can not be browsed and  when you use the find the link to 
> the jar is 
> > wrong and an 404 error occurs because the path is linked to 
> > 
> http://localhost:8081/repository//com/knudsen/utility/1.0/utility.pom
> > that is not existing.
> Archiva scans the repository periodically, so files directly 
> dropped into its directories won't get picked up right away. 
> You may have to wait for... however long it is configured in 
> your installation. 8-)
> Also you could try the "Scan Repository Now" button to start 
> an immediate scan. I know it's not automatic, but you can 
> test if the publishing is successful.

Also, Archiva is very strict about enforcing Maven's layout convention,
so if your artifact file name doesn't contain your module name, you're
out of luck.  It cannot be browsed and it will not generate Maven
metadata.   Why do you care about Maven metadata?  Because Archiva won't
allow directory listing, which Ivy needs to determine the available
revisions.  Furthermore, Archiva seems only to want to expose artifacts
of type *.jar, *.pom, and maven-metadata.xml.   Furthermore, if you're
publishing artifacts directly to the filesystem with Archiva, sometimes
they simply won't get indexed at all.

I spent several frustrating weeks month trying to make Archiva function
in a way suitable to my needs.  My conclusion re Archiva, stated in the
most diplomatic possible way, is that Archiva and Maven are a good fit
for one another.   Regarding artifact proxies in general, and fancy
web-based repository managers, these are a nice convenience but really
give no business value over using a straight NFS or SMB file share.
Your needs may vary, of course.

This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the 
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on 
the contents of this message is prohibited. In such
case please notify us and destroy and delete all 
copies of this transmission.  Thank you.

View raw message