More to the point, it's hard to imagine a useful pattern which doesn't include organization and module, and probably type (you would had to end up with a source and javadoc jar having the same location/name as the binary jar).
Also, you'll want to add the ivy pattern as well. It's typical to structure the repo: org/module/ivys/ivy-x.x.x.xml org/module/jars/module-x.x.x.jar org/module/javadocs/module-x.x.x.zip Thanks, --- Kirby Files Software Architect Masergy Communications, Inc. [email protected] ________________________________________ From: Richard_Senior [[email protected]] Sent: Wednesday, March 23, 2011 12:53 PM To: [email protected] Subject: Re: Publishing... Ach... fixed part of my problem.. I was missing the revision in the pattern ; should have been ${dist.dir.live}/[artifact].[revision].[ext] -- View this message in context: http://old.nabble.com/Publishing...-tp31221641p31221704.html Sent from the ivy-user mailing list archive at Nabble.com.
