I want to suggest a simple yet powerful idea: store all of your directory structure inside a ZIP file (Ant already has core zip task) and publish it as a single artifact.
This keeps both your project design and ivy design simpler. In your project, you don't have to deal with many configurations, and nor with many retrieves when you use the published module. In my suggestion you just get the zip file the standard way (by ivy:retrieve or directly by using ivy:cachefileset) and unzip it using standard Ant task. easyproglife. On 1/4/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
Ivy does not support this kind of thing, but there's already an issue about directory publication, what could also be done is allow artifact names with slashes. You can submit an issue for that if you want. Xavier On 1/4/07, Eric Crahen <[EMAIL PROTECTED]> wrote: > > If I wanted to store some artifacts and preserve a directory structure, is > there someway to do this? > For instance, I might have some ".xml" artifacts that have to live in > certain directories: > > conf/ > base.xml > ext/ > ext.xml > > I have several configuration packages that depend on one another and > ultimately, the > leaf nodes of the tree build different jars of configuration, where some > config is shared. > > It seems that the closest I can get is to use a series of publish/resolve, > where I need > to change the patterns each time. Or I'd need to jar everything and > unjar/rejar when I > compile everything in the end. > > I tried just including /'s in the artifact names but Ivy does not respect > that as a file separator. > > -- > > - Eric > >
