> -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 04, 2008 2:59 AM > To: [email protected] > Subject: Re: Status of ivy repository > > On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton < > [EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > > > Sent: Monday, March 03, 2008 3:27 PM > > > To: [email protected] > > > Subject: Re: Status of ivy repository > > > > > > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton < > > > [EMAIL PROTECTED]> wrote: > > > > > > > I would like to know every case where Ivy can read a Maven pom > > > > file and use this information for resolution, file generation, > > > or any other > > > > purpose. > > > > > > Ivy understand poms as it understands ivy files: you have > parser for > > > each, and you can do pretty much everything supported by > each format > > > with both. > > > Whenever your file has a pom extension, Ivy will use the > pom parser. > > > > You're referring to the ibiblio resolver, right? Or is there some > > other place when ivy would implicitly use the pom file? > > It doesn't really depend on the resolver... well, ibiblio > resolver in m2compatible mode actually attempts to find a > module descriptor using the pom extension, so you don't have > to do anything special. But if you configure any resolver > with a pattern for "ivy" ending with .pom, it will use the > pom parser to parse it. The name "ivy" for the pattern is > confusing, that's why I suggested to accept "descriptor" or > "metadata" as an alternative. But it already works like that, > you can use any module descriptor format in any resolver, you > just have to supply the good parser (ivy files and poms being > supported out of the box, but you can plug your own).
What if I have a repository where some artifacts have ivy files and others have pom files? An ibiblio resolver cannot declare an ivy pattern, and a url resolver cannot declare usepoms=true. I guess I could have 2 different resolvers point to the same URL. Or maybe mixing repositories is just a bad idea? ----------------------------------------- ==================================================== This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you. ====================================================
