Thanks for the reply, ON further examination it is doing as you describe.
1. Search for all artifacts in conf. 2. Download all artifacts in conf. 3. Filter by type and place only those artifacts on the classpath. Can this be modified so we only download the artifacts that are filtered. Or at least have a attribute to turn it on? I can see this functionality being more obvious: 1. Search for all artifacts in conf of type="x(,y...)" 2. Download only these artifacts Completely ignoring any of the wrong type. What do you guys think? Alex Foreman Morgan Stanley | Technology 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW Phone: +44 20 7677-5732 [EMAIL PROTECTED] -----Original Message----- From: Xavier Hanin [mailto:[EMAIL PROTECTED] Sent: 28 March 2008 14:29 To: [email protected] Subject: Re: IvyDE Accepted Types On Fri, Mar 28, 2008 at 11:29 AM, Foreman, Alex (IT) < [EMAIL PROTECTED]> wrote: > I have set Accepted types to: > jar, zip, dll > > Within IvyDE > > I have a ivyfile which defines a list of .so files and .dll files. > All in the same configuration. > > I want to grab stuff by type only. > > When building on unix I want to say: > Give me this module and all its artifacts that are .so types only > > Eg > Artifact -> x.dll > Artifact -> y.dll > Artifact -> z.so > > Would return just z.so as type="jar,so" > > This doesn't seem to work in unix either or from the dos shell. > <ivy:cachepath pathid="tests" conf="jni" type="so" useOrigin="true" /> > Grabs everything in the configuration regardless of type. > > Is this a bug? Missing functionality? As according to this page: > http://ant.apache.org/ivy/history/latest-milestone/use/cachepath.html > This is what 'type' does. > > This is a major blocker for me. If I can say grab everything that is > of types x and y and ignore everything else then I have pretty much > solved my problems with getting JNIs working It should work. But note that the filter is applied by cachepath only, not by the resolve. So Ivy will actually download all artifacts, but only so should be in your path 'tests' after the call to cachepath. If it doesn't work like that, you can open an issue, describing precisely how you call cachepath, what is your ivy file for the dependency, and what you get in your path. Xavier > without hassle. > > > Many thanks for your help, > > Alex Foreman > Morgan Stanley | Technology > 20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW > Phone: +44 20 7677-5732 > [EMAIL PROTECTED] > -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. Sender > does not intend to waive confidentiality or privilege. Use of this > email is prohibited when received in error. > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
