On Tue, Mar 4, 2008 at 4:20 PM, Brown, Carlton < [EMAIL PROTECTED]> wrote:
> > > > -----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). > > Thanks, I thought that is what you meant, and this is certainly > intuitive behavior. I just was not able to be 100% certain from the > documentation. If you have ideas on how to improve it, feel free to contribute a patch! > > > Like the <ivy> pattern name is confusing, I also find the resolver name > "ibiblio" somewhat confusing as well. I agree, and I've recently discussed introducing a maven2 resolver. Maybe we could simply deprecate ibiblio, and create a maven resolver with m2compatible="true" by default. > I can't see how it is any > different from the <url> resolver except that it uses pom files to > resolve the dependency graph. The settings are slightly different, isolating the root from the paths, which make it easier to use but also more limited. The default for the root is very maven specific too. We also have some specific behaviour in this resolver, like disabling the listing of organizations and modules (due to very bad performance when accessing corresponding pages due to the high number of elements) and support for maven-metadata.xml. You could just get rid of the ibiblio > resolver altogether as well as the ivy pattern and do something like > this: > <resolver name="foo"> > <url name="foo-url" root="http://myreposerver/myrepo/";> > <artifact > pattern="[organisation]/[module]/[revision]/[artifact].[ext]"/> > <schema type="maven2"> > > <pattern="[organisation]/[module]/[revision]/[resolution]-[revision].[ex > t]"/> > </schema> > </url> > </resolver> > > This way your resolver would be coupled to a resolution schema instead > of a file extension. Then the ibiblio resolver would become > unnecessary. This is just another way of doing very similar things. I'm not sure it would really help, it's more a matter of taste. Maybe others have an opinion to give on this subject? Xavier > > > ----------------------------------------- > ==================================================== > 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. > ==================================================== > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
