You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Brown, Carlton" <Ca...@compucredit.com> on 2008/03/03 19:18:31 UTC
Status of ivy repository
Hi all,
I notice that there is a location labeled "official ivy repository" at
http://www.jayasoft.fr/org/ivyrep/
Is it still considered authoritative, and it is actively maintained?
If not, is there some other public repository of ivy files and/or
artifacts?
It occurs to me that the resolution of open-source transitive
dependencies is only as reliable as the metadata repository. I notice
that this official ivyrep has only 29 modules, not very much. It seems
that if our applications depend on many open-source modules, then we
must invest a lot of time in creating Ivy files corresponding to the pom
files in Maven central. Is that an accurate assumption? Or is there
some helper tool that can generate this for us?
Thanks,
Carlton
-----------------------------------------
====================================================
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.
====================================================
Re: Status of ivy repository
Posted by Xavier Hanin <xa...@gmail.com>.
On Thu, Mar 6, 2008 at 9:08 PM, Brown, Carlton <
Carlton.Brown@compucredit.com> wrote:
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Tuesday, March 04, 2008 2:59 AM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Status of ivy repository
> >
> > On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton <
> > Carlton.Brown@compucredit.com> wrote:
> >
> > > > -----Original Message-----
> > > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > > Sent: Monday, March 03, 2008 3:27 PM
> > > > To: ivy-user@ant.apache.org
> > > > Subject: Re: Status of ivy repository
> > > >
> > > > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> > > > Carlton.Brown@compucredit.com> 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?
You can use something like that in a URL resolver:
<ivy pattern="http://repo/[module]/[revision]/ivy.xml" />
<ivy pattern="http://repo/[module]/[revision]/[module].pom" />
And the resolver will be able to locate both types of metadata.
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/
RE: Status of ivy repository
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Tuesday, March 04, 2008 2:59 AM
> To: ivy-user@ant.apache.org
> Subject: Re: Status of ivy repository
>
> On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton <
> Carlton.Brown@compucredit.com> wrote:
>
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > Sent: Monday, March 03, 2008 3:27 PM
> > > To: ivy-user@ant.apache.org
> > > Subject: Re: Status of ivy repository
> > >
> > > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> > > Carlton.Brown@compucredit.com> 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.
====================================================
Re: Status of ivy repository
Posted by Xavier Hanin <xa...@gmail.com>.
On Tue, Mar 4, 2008 at 4:20 PM, Brown, Carlton <
Carlton.Brown@compucredit.com> wrote:
>
>
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Tuesday, March 04, 2008 2:59 AM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Status of ivy repository
> >
> > On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton <
> > Carlton.Brown@compucredit.com> wrote:
> >
> > > > -----Original Message-----
> > > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > > Sent: Monday, March 03, 2008 3:27 PM
> > > > To: ivy-user@ant.apache.org
> > > > Subject: Re: Status of ivy repository
> > > >
> > > > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> > > > Carlton.Brown@compucredit.com> 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/
RE: Status of ivy repository
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Tuesday, March 04, 2008 2:59 AM
> To: ivy-user@ant.apache.org
> Subject: Re: Status of ivy repository
>
> On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton <
> Carlton.Brown@compucredit.com> wrote:
>
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > Sent: Monday, March 03, 2008 3:27 PM
> > > To: ivy-user@ant.apache.org
> > > Subject: Re: Status of ivy repository
> > >
> > > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> > > Carlton.Brown@compucredit.com> 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.
Like the <ivy> pattern name is confusing, I also find the resolver name
"ibiblio" somewhat confusing as well. I can't see how it is any
different from the <url> resolver except that it uses pom files to
resolve the dependency graph. 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 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.
====================================================
Re: Status of ivy repository
Posted by Xavier Hanin <xa...@gmail.com>.
On Mon, Mar 3, 2008 at 10:48 PM, Brown, Carlton <
Carlton.Brown@compucredit.com> wrote:
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Monday, March 03, 2008 3:27 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Status of ivy repository
> >
> > On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> > Carlton.Brown@compucredit.com> 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).
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/
RE: Status of ivy repository
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Monday, March 03, 2008 3:27 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Status of ivy repository
>
> On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
> Carlton.Brown@compucredit.com> 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?
-----------------------------------------
====================================================
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.
====================================================
Re: Status of ivy repository
Posted by Xavier Hanin <xa...@gmail.com>.
On Mon, Mar 3, 2008 at 8:30 PM, Brown, Carlton <
Carlton.Brown@compucredit.com> wrote:
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: Monday, March 03, 2008 2:21 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Status of ivy repository
> > > Ivy is able to parse maven 2 poms and convert it in Ivy
> > files. The resulting Ivy files aren't as clean as if they
> > were written by hand, no magic here, but it works really
> > well, and we are regularly improving our support. So you can
> > either use maven 2 repo directly, or use install task to get
> > the jars and the converted poms under your control. Isn't
> > life beautiful ? ;-)
>
> Yes, that's good news indeed. Can you explain which Ivy task converts
> the pom to ivy.xml ? I don't see any explanation of this in the
> documentation, except there is a small hint in the repository tutorial.
I thought the repository tutorial was pretty clear, if you look at the
example "install a module with dependencies", at the end there is this:
"As you can see there is no pom here (pom is the module metadata format used
by maven 2, available on the maven 2 repository). Instead you can see
there's an ivy file, which is actually the original hibernate pom converted
into an ivy file."
The adjusting default settings tutorial says this:
"the public repository is ibiblio in m2 compatible mode (in other words, the
maven 2 public repository).
This repository has the advantage of providing a lot of modules, with
metadata for most of them."
Which means that Ivy is able to leverage metadata found in maven 2 repo, i.e.
poms.
On the ibiblio resolver doc we have this:
"Using the m2compatible attribute, you can benefit from maven 2 repository
compatibility (convert dots in organisation in slashes, search for poms, use
transitive dependencies of poms)."
Sounds pretty clear. Except that I agree we do not explain that poms are
actually converted in ivy files, but this is useful only if you want to
install modules.
So to answer your question there is no documented task to convert a pom to
an ivy file. The usual way is to use the install task. Alternatively you can
use the ivy:convertpom task, which is not documented :-( Here is an example:
<ivy:convertpom pomFile="pom.xml" ivyFile="ivy.xml" />
> 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. The
only thing we don't support with poms is deliver/publish. Indeed we have no
updater/writer for poms, only a parser. But the makepom task can help to
generate a pom from your ivy file.
HTH,
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/
RE: Status of ivy repository
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: Monday, March 03, 2008 2:21 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Status of ivy repository
> > Ivy is able to parse maven 2 poms and convert it in Ivy
> files. The resulting Ivy files aren't as clean as if they
> were written by hand, no magic here, but it works really
> well, and we are regularly improving our support. So you can
> either use maven 2 repo directly, or use install task to get
> the jars and the converted poms under your control. Isn't
> life beautiful ? ;-)
Yes, that's good news indeed. Can you explain which Ivy task converts
the pom to ivy.xml ? I don't see any explanation of this in the
documentation, except there is a small hint in the repository tutorial.
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.
-----------------------------------------
====================================================
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.
====================================================
Re: Status of ivy repository
Posted by Xavier Hanin <xa...@gmail.com>.
On Mon, Mar 3, 2008 at 7:50 PM, Brown, Carlton <
Carlton.Brown@compucredit.com> wrote:
> > -----Original Message-----
> > From: Gilles Scokart [mailto:gscokart@gmail.com]
> > Sent: Monday, March 03, 2008 1:40 PM
> > To: ivy-user@ant.apache.org
> > Subject: Re: Status of ivy repository
> >
> >
> > You can actually use the install task in order to build your
> > own repository and patch it when required.
>
> As far as I know, the install task essentially only copies artifacts
> from one resolver to another resolver. That means I can copy the
> modules and pom files from Maven central into my own repository.
> However, Ivy cannot use Maven pom files for resolution, can it? Isn't
> it true that if I want full transitive resolution for the install
> modules, I must somehow generate an Ivy file from the Maven pom file,
> probably by hand?
Ivy is able to parse maven 2 poms and convert it in Ivy files. The resulting
Ivy files aren't as clean as if they were written by hand, no magic here,
but it works really well, and we are regularly improving our support. So you
can either use maven 2 repo directly, or use install task to get the jars
and the converted poms under your control. Isn't life beautiful ? ;-)
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/
RE: Status of ivy repository
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
> -----Original Message-----
> From: Gilles Scokart [mailto:gscokart@gmail.com]
> Sent: Monday, March 03, 2008 1:40 PM
> To: ivy-user@ant.apache.org
> Subject: Re: Status of ivy repository
>
>
> You can actually use the install task in order to build your
> own repository and patch it when required.
As far as I know, the install task essentially only copies artifacts
from one resolver to another resolver. That means I can copy the
modules and pom files from Maven central into my own repository.
However, Ivy cannot use Maven pom files for resolution, can it? Isn't
it true that if I want full transitive resolution for the install
modules, I must somehow generate an Ivy file from the Maven pom file,
probably by hand?
-----------------------------------------
====================================================
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.
====================================================
Re: Status of ivy repository
Posted by Gilles Scokart <gs...@gmail.com>.
On 03/03/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
>
> Hi all,
>
> I notice that there is a location labeled "official ivy repository" at
> http://www.jayasoft.fr/org/ivyrep/
>
> Is it still considered authoritative, and it is actively maintained?
It is not.
If not, is there some other public repository of ivy files and/or
> artifacts?
We are relying on the maven central repository.
The good thing with this repository is that it is "big" and rather complete.
The bad thing is that the pom are not always as clean as it should.
It occurs to me that the resolution of open-source transitive
> dependencies is only as reliable as the metadata repository. I notice
> that this official ivyrep has only 29 modules, not very much. It seems
> that if our applications depend on many open-source modules, then we
> must invest a lot of time in creating Ivy files corresponding to the pom
> files in Maven central. Is that an accurate assumption? Or is there
> some helper tool that can generate this for us?
You can actually use the install task in order to build your own repository
and patch it when required.
--
Gilles Scokart