It can also go into ivysettings.xml (see example: http://ant.apache.org/ivy/history/latest-milestone/settings.html) and you can pass via properties where this file is, if not in classpath).
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Greg Bowyer [mailto:[email protected]] > Sent: Friday, March 30, 2012 11:43 PM > To: [email protected] > Subject: Re: ivy. > > I am pretty sure this needs to go into the ivy.xml in lucene proper > > On 30/03/12 13:46, Dawid Weiss wrote: > > Ah, that's what I was looking for. But where do I put it? Can we set > > it globally in Lucene so that others (who have .m2 repos) can make > > immediate use of their preloaded artefacts? > > > > D. > > > > On Fri, Mar 30, 2012 at 10:44 PM, Greg Bowyer<[email protected]> > wrote: > >> You can get ivy to treat the local maven repo as a resolver host I > >> think the required config is along the lines of > >> > >> ---- %< ---- > >> <resolvers> > >> <filesystem name="local-maven-2" m2compatible="true" force="false" > >> local="true"> > >> <artifact > >> pattern="${gerald.repo.dir}/[organisation]/[module]/[revision]/[modul > >> e]-[revision].[ext]"/> > >> <ivy > >> pattern="${gerald.repo.dir}/[organisation]/[module]/[revision]/[modul > >> e]-[revision].pom"/> > >> </filesystem> > >> </resolvers> > >> ... > >> </settings> > >> > >> <chain name="whatever" dual="true" > >> checkmodified="true" changingPattern=".*SNAPSHOT"> <resolver > >> ref="local-maven-2"/> <resolver ref="apache-snapshot"/> <resolver > >> ref="maven2"/> > >> ... > >> </chain> > >> > >> ---->% ---- > >> > >> -- Greg > >> > >> > >> On 30/03/12 13:27, Dawid Weiss wrote: > >>>> But honestly, i have no idea how ivy works. its just like ant to > >>>> me. i just hack and hack and hack until it works. > >>> You're a live randomized solver! > >>> > >>> Dawid > >>> > >>> -------------------------------------------------------------------- > >>> - To unsubscribe, e-mail: [email protected] For > >>> additional commands, e-mail: [email protected] > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] For > >> additional commands, e-mail: [email protected] > >> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
