Yes, please see my previous posts on this topic (by searching the archives) as I also use a configuration for each platform and it works very nicely.
--- Shawn Castrianni -----Original Message----- From: Steve Miller [mailto:thatguy1...@gmail.com] Sent: Wednesday, September 29, 2010 12:00 PM To: ivy-user@ant.apache.org Subject: Re: Using Ivy to manage platform dependent non-java binaries I don't think you need multiple repositories. Just create an ivy.xml module file that has multiple configurations and multiple artifacts in the publications section. Then publish that module to your repository. Then all other projects can ask for whichever artifact it needs. Maybe see the configurations tutorial. I think that has an example of multiple artifacts. http://ant.apache.org/ivy/history/latest-milestone/tutorial/conf.html Steve On Wed, Sep 29, 2010 at 12:42 PM, Eelamae <eela...@yahoo.com> wrote: > > Correction: Actually the artifact patter is as follws; > > <chain name="rt2binaries"> > > <filesystem name="linux-ia32" checkmodified="yes" > cache="rt2-linux-ia32-cache"> > <artifact > pattern="/work/project/repos/external/bin/linux-ia32//[artifact]" /> > </filesystem> > > <filesystem name="solaris-sparc" checkmodified="yes" > cache="rt2-solaris-sparc-cache"> > <artifact > pattern="/work/project/repos/external/bin/solaris-sparc/[artifact]" /> > </filesystem> > > <filesystem name="windows-ia32" checkmodified="yes" > cache="rt2-windows-ia32-cache"> > <artifact > pattern="/work/project/repos/external/bin/windows-ia32/[artifact].[ext]" /> > </filesystem> > > </chain> > </resolvers> > -- > View this message in context: > http://old.nabble.com/Using-Ivy-to-manage-platform-dependent-non-java-binaries-tp29840412p29840471.html > Sent from the ivy-user mailing list archive at Nabble.com. > > ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
