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 nirvdrum <km...@servprise.com> on 2007/05/25 19:30:56 UTC
Dealing with bad POMs?
Hi,
As noted earlier, I'm looking to move from maven2 over to ant+ivy. During
the migration, I've run across problems with a few POMs on ibiblio. maven2
apparently deals with the problems okay, since I never had problems
downloading the files. ivy doesn't seem to allow me to. Is there anyway to
tell ivy to download the files no matter what?
As an example of the problems, one POM marks a version as 4.0.1, while the
artifact is actually at version 4.0.2. ivy finds the files in the correct
path, but then compares against the POM and borks when the versions don't
match.
In another, the organization defined in the POM does not match that used as
the path to the artifact. Once again, ivy finds the file fine, but borks
when doing a consistency check on the POM.
Any help would be much appreciated.
Thanks,
Kevin
--
View this message in context: http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
Sent from the ivy-user mailing list archive at Nabble.com.
Re: Dealing with bad POMs?
Posted by Xavier Hanin <xa...@gmail.com>.
checkconsistency is (slightly) documented here:
http://incubator.apache.org/ivy/doc/configuration/resolvers.html
The consistency check disabled is the check that the module descriptor found
contains meta information consistent with the meta information of the
dependency descriptor which has lead to the module descriptor.
Xavier
On 5/31/07, Gilles Scokart <gs...@gmail.com> wrote:
>
> Hmm, checkconsistency is not documented. What does it do? What are
> the consistency checks disabled? Is it a particular reason to not
> document it?
>
> Gilles
>
> 2007/5/29, Xavier Hanin <xa...@gmail.com>:
> > I agree with Gilles, you should raise an issue in maven repository jira.
> >
> > OTOH setting up a private repository can be done only to fix some poms:
> you
> > can store only the fixed pom in your private repo, and use maven one for
> the
> > rest. In this case you don't have to much trouble to set it up, it can
> be as
> > simple as a simple directory checked out with your project. Here is an
> > example of resolver setup:
> > <chain name="fixed-ibiblio" dual="true">
> > <file name="fixed-poms">
> > <ivy
> >
> pattern="path/to/fixed/pom/repo/[organisation]/[module]/[revision]/pom-[revision].xml"
> > />
> > </file>
> > /your ibiblio resolver here/
> > </chain>
> >
> > Another solution which should be even simpler in this case (where you
> only
> > have a problem of revision in the public pom) is to disable consistency
> > checking in Ivy for the resolver causing problem. For instance:
> > <ibiblio name="public" checkconsistency=false" m2compatible="true" />
> >
> > HTH,
> >
> > Xavier
> >
> > On 5/27/07, nirvdrum <km...@servprise.com> wrote:
> > >
> > >
> > > Alright. I can certainly raise issues with them, but the maven tool
> > > itself
> > > is resilient to these types of errors. This seems like a case of "fix
> it
> > > in
> > > one place once" or "fix it many places, many times". I'll raise a
> JIRA in
> > > ivy, too, since the tool should also allow some sort of override
> here. If
> > > it can detect the failure, it should have the ability to ignore it,
> too.
> > >
> > > Setting up a private repository isn't really all that ideal either. I
> was
> > > hoping to use ivy since I read about how it was much easier and
> quicker to
> > > use than maven.
> > >
> > > Thanks for the response though,
> > > Kevin
> > >
> > >
> > > Gilles Scokart wrote:
> > > >
> > > > I guess the best thing to do is to raise an issue in
> > > > http://jira.codehaus.org/browse/MEV as described there :
> > > > http://maven.apache.org/guides/mini/guide-maven-evangelism.html. The
> > > > thing you describe are clearly errors in the repository.
> > > >
> > > > As a workaround, you can may try to use an other repository where
> you
> > > > can install the correct poms (or ivy.xml files). Maybe using a dual
> > > > resolver.
> > > >
> > > > Note also that ivy can work with a repository without pom.xml nor
> > > > ivy.xml when the modules have no dependencies.
> > > >
> > > > I hope it helps.
> > > >
> > > > Gilles
> > > >
> > > > 2007/5/25, nirvdrum <km...@servprise.com>:
> > > >>
> > > >> Hi,
> > > >>
> > > >> As noted earlier, I'm looking to move from maven2 over to ant+ivy.
> > > >> During
> > > >> the migration, I've run across problems with a few POMs on ibiblio.
> > > >> maven2
> > > >> apparently deals with the problems okay, since I never had problems
> > > >> downloading the files. ivy doesn't seem to allow me to. Is there
> > > anyway
> > > >> to
> > > >> tell ivy to download the files no matter what?
> > > >>
> > > >> As an example of the problems, one POM marks a version as 4.0.1,
> while
> > > >> the
> > > >> artifact is actually at version 4.0.2. ivy finds the files in the
> > > >> correct
> > > >> path, but then compares against the POM and borks when the versions
> > > don't
> > > >> match.
> > > >>
> > > >> In another, the organization defined in the POM does not match that
> > > used
> > > >> as
> > > >> the path to the artifact. Once again, ivy finds the file fine, but
> > > borks
> > > >> when doing a consistency check on the POM.
> > > >>
> > > >> Any help would be much appreciated.
> > > >>
> > > >> Thanks,
> > > >> Kevin
> > > >> --
> > > >> View this message in context:
> > > >>
> http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
> > > >> Sent from the ivy-user mailing list archive at Nabble.com.
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Gilles SCOKART
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> > > http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10828209
> > > Sent from the ivy-user mailing list archive at Nabble.com.
> > >
> > >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > Manage your dependencies with Ivy!
> > http://incubator.apache.org/ivy/
> >
>
>
> --
> Gilles SCOKART
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
Re: Dealing with bad POMs?
Posted by Gilles Scokart <gs...@gmail.com>.
Hmm, checkconsistency is not documented. What does it do? What are
the consistency checks disabled? Is it a particular reason to not
document it?
Gilles
2007/5/29, Xavier Hanin <xa...@gmail.com>:
> I agree with Gilles, you should raise an issue in maven repository jira.
>
> OTOH setting up a private repository can be done only to fix some poms: you
> can store only the fixed pom in your private repo, and use maven one for the
> rest. In this case you don't have to much trouble to set it up, it can be as
> simple as a simple directory checked out with your project. Here is an
> example of resolver setup:
> <chain name="fixed-ibiblio" dual="true">
> <file name="fixed-poms">
> <ivy
> pattern="path/to/fixed/pom/repo/[organisation]/[module]/[revision]/pom-[revision].xml"
> />
> </file>
> /your ibiblio resolver here/
> </chain>
>
> Another solution which should be even simpler in this case (where you only
> have a problem of revision in the public pom) is to disable consistency
> checking in Ivy for the resolver causing problem. For instance:
> <ibiblio name="public" checkconsistency=false" m2compatible="true" />
>
> HTH,
>
> Xavier
>
> On 5/27/07, nirvdrum <km...@servprise.com> wrote:
> >
> >
> > Alright. I can certainly raise issues with them, but the maven tool
> > itself
> > is resilient to these types of errors. This seems like a case of "fix it
> > in
> > one place once" or "fix it many places, many times". I'll raise a JIRA in
> > ivy, too, since the tool should also allow some sort of override here. If
> > it can detect the failure, it should have the ability to ignore it, too.
> >
> > Setting up a private repository isn't really all that ideal either. I was
> > hoping to use ivy since I read about how it was much easier and quicker to
> > use than maven.
> >
> > Thanks for the response though,
> > Kevin
> >
> >
> > Gilles Scokart wrote:
> > >
> > > I guess the best thing to do is to raise an issue in
> > > http://jira.codehaus.org/browse/MEV as described there :
> > > http://maven.apache.org/guides/mini/guide-maven-evangelism.html . The
> > > thing you describe are clearly errors in the repository.
> > >
> > > As a workaround, you can may try to use an other repository where you
> > > can install the correct poms (or ivy.xml files). Maybe using a dual
> > > resolver.
> > >
> > > Note also that ivy can work with a repository without pom.xml nor
> > > ivy.xml when the modules have no dependencies.
> > >
> > > I hope it helps.
> > >
> > > Gilles
> > >
> > > 2007/5/25, nirvdrum <km...@servprise.com>:
> > >>
> > >> Hi,
> > >>
> > >> As noted earlier, I'm looking to move from maven2 over to ant+ivy.
> > >> During
> > >> the migration, I've run across problems with a few POMs on ibiblio.
> > >> maven2
> > >> apparently deals with the problems okay, since I never had problems
> > >> downloading the files. ivy doesn't seem to allow me to. Is there
> > anyway
> > >> to
> > >> tell ivy to download the files no matter what?
> > >>
> > >> As an example of the problems, one POM marks a version as 4.0.1, while
> > >> the
> > >> artifact is actually at version 4.0.2. ivy finds the files in the
> > >> correct
> > >> path, but then compares against the POM and borks when the versions
> > don't
> > >> match.
> > >>
> > >> In another, the organization defined in the POM does not match that
> > used
> > >> as
> > >> the path to the artifact. Once again, ivy finds the file fine, but
> > borks
> > >> when doing a consistency check on the POM.
> > >>
> > >> Any help would be much appreciated.
> > >>
> > >> Thanks,
> > >> Kevin
> > >> --
> > >> View this message in context:
> > >> http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
> > >> Sent from the ivy-user mailing list archive at Nabble.com.
> > >>
> > >>
> > >
> > >
> > > --
> > > Gilles SCOKART
> > >
> > >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10828209
> > Sent from the ivy-user mailing list archive at Nabble.com.
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant
> Manage your dependencies with Ivy!
> http://incubator.apache.org/ivy/
>
--
Gilles SCOKART
Re: Dealing with bad POMs?
Posted by Xavier Hanin <xa...@gmail.com>.
I agree with Gilles, you should raise an issue in maven repository jira.
OTOH setting up a private repository can be done only to fix some poms: you
can store only the fixed pom in your private repo, and use maven one for the
rest. In this case you don't have to much trouble to set it up, it can be as
simple as a simple directory checked out with your project. Here is an
example of resolver setup:
<chain name="fixed-ibiblio" dual="true">
<file name="fixed-poms">
<ivy
pattern="path/to/fixed/pom/repo/[organisation]/[module]/[revision]/pom-[revision].xml"
/>
</file>
/your ibiblio resolver here/
</chain>
Another solution which should be even simpler in this case (where you only
have a problem of revision in the public pom) is to disable consistency
checking in Ivy for the resolver causing problem. For instance:
<ibiblio name="public" checkconsistency=false" m2compatible="true" />
HTH,
Xavier
On 5/27/07, nirvdrum <km...@servprise.com> wrote:
>
>
> Alright. I can certainly raise issues with them, but the maven tool
> itself
> is resilient to these types of errors. This seems like a case of "fix it
> in
> one place once" or "fix it many places, many times". I'll raise a JIRA in
> ivy, too, since the tool should also allow some sort of override here. If
> it can detect the failure, it should have the ability to ignore it, too.
>
> Setting up a private repository isn't really all that ideal either. I was
> hoping to use ivy since I read about how it was much easier and quicker to
> use than maven.
>
> Thanks for the response though,
> Kevin
>
>
> Gilles Scokart wrote:
> >
> > I guess the best thing to do is to raise an issue in
> > http://jira.codehaus.org/browse/MEV as described there :
> > http://maven.apache.org/guides/mini/guide-maven-evangelism.html . The
> > thing you describe are clearly errors in the repository.
> >
> > As a workaround, you can may try to use an other repository where you
> > can install the correct poms (or ivy.xml files). Maybe using a dual
> > resolver.
> >
> > Note also that ivy can work with a repository without pom.xml nor
> > ivy.xml when the modules have no dependencies.
> >
> > I hope it helps.
> >
> > Gilles
> >
> > 2007/5/25, nirvdrum <km...@servprise.com>:
> >>
> >> Hi,
> >>
> >> As noted earlier, I'm looking to move from maven2 over to ant+ivy.
> >> During
> >> the migration, I've run across problems with a few POMs on ibiblio.
> >> maven2
> >> apparently deals with the problems okay, since I never had problems
> >> downloading the files. ivy doesn't seem to allow me to. Is there
> anyway
> >> to
> >> tell ivy to download the files no matter what?
> >>
> >> As an example of the problems, one POM marks a version as 4.0.1, while
> >> the
> >> artifact is actually at version 4.0.2. ivy finds the files in the
> >> correct
> >> path, but then compares against the POM and borks when the versions
> don't
> >> match.
> >>
> >> In another, the organization defined in the POM does not match that
> used
> >> as
> >> the path to the artifact. Once again, ivy finds the file fine, but
> borks
> >> when doing a consistency check on the POM.
> >>
> >> Any help would be much appreciated.
> >>
> >> Thanks,
> >> Kevin
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
> >> Sent from the ivy-user mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Gilles SCOKART
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10828209
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
Re: Dealing with bad POMs?
Posted by Steve Loughran <st...@apache.org>.
nirvdrum wrote:
> Alright. I can certainly raise issues with them, but the maven tool itself
> is resilient to these types of errors.
well, the tool may be resilient but really the process should be robust
against dirty data getting up on the repository. If you do find
inconsistencies on the central repositories, let us know and we will
take it up with the repository manager (carlos). Normally the team has a
'no updates to published' metadata, but illegal metadata may be a
special case (rather than dependency data, which can be wrong but not
invalid)
-steve
Re: Dealing with bad POMs?
Posted by nirvdrum <km...@servprise.com>.
Alright. I can certainly raise issues with them, but the maven tool itself
is resilient to these types of errors. This seems like a case of "fix it in
one place once" or "fix it many places, many times". I'll raise a JIRA in
ivy, too, since the tool should also allow some sort of override here. If
it can detect the failure, it should have the ability to ignore it, too.
Setting up a private repository isn't really all that ideal either. I was
hoping to use ivy since I read about how it was much easier and quicker to
use than maven.
Thanks for the response though,
Kevin
Gilles Scokart wrote:
>
> I guess the best thing to do is to raise an issue in
> http://jira.codehaus.org/browse/MEV as described there :
> http://maven.apache.org/guides/mini/guide-maven-evangelism.html . The
> thing you describe are clearly errors in the repository.
>
> As a workaround, you can may try to use an other repository where you
> can install the correct poms (or ivy.xml files). Maybe using a dual
> resolver.
>
> Note also that ivy can work with a repository without pom.xml nor
> ivy.xml when the modules have no dependencies.
>
> I hope it helps.
>
> Gilles
>
> 2007/5/25, nirvdrum <km...@servprise.com>:
>>
>> Hi,
>>
>> As noted earlier, I'm looking to move from maven2 over to ant+ivy.
>> During
>> the migration, I've run across problems with a few POMs on ibiblio.
>> maven2
>> apparently deals with the problems okay, since I never had problems
>> downloading the files. ivy doesn't seem to allow me to. Is there anyway
>> to
>> tell ivy to download the files no matter what?
>>
>> As an example of the problems, one POM marks a version as 4.0.1, while
>> the
>> artifact is actually at version 4.0.2. ivy finds the files in the
>> correct
>> path, but then compares against the POM and borks when the versions don't
>> match.
>>
>> In another, the organization defined in the POM does not match that used
>> as
>> the path to the artifact. Once again, ivy finds the file fine, but borks
>> when doing a consistency check on the POM.
>>
>> Any help would be much appreciated.
>>
>> Thanks,
>> Kevin
>> --
>> View this message in context:
>> http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
>> Sent from the ivy-user mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Gilles SCOKART
>
>
--
View this message in context: http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10828209
Sent from the ivy-user mailing list archive at Nabble.com.
Re: Dealing with bad POMs?
Posted by Gilles Scokart <gs...@gmail.com>.
I guess the best thing to do is to raise an issue in
http://jira.codehaus.org/browse/MEV as described there :
http://maven.apache.org/guides/mini/guide-maven-evangelism.html . The
thing you describe are clearly errors in the repository.
As a workaround, you can may try to use an other repository where you
can install the correct poms (or ivy.xml files). Maybe using a dual
resolver.
Note also that ivy can work with a repository without pom.xml nor
ivy.xml when the modules have no dependencies.
I hope it helps.
Gilles
2007/5/25, nirvdrum <km...@servprise.com>:
>
> Hi,
>
> As noted earlier, I'm looking to move from maven2 over to ant+ivy. During
> the migration, I've run across problems with a few POMs on ibiblio. maven2
> apparently deals with the problems okay, since I never had problems
> downloading the files. ivy doesn't seem to allow me to. Is there anyway to
> tell ivy to download the files no matter what?
>
> As an example of the problems, one POM marks a version as 4.0.1, while the
> artifact is actually at version 4.0.2. ivy finds the files in the correct
> path, but then compares against the POM and borks when the versions don't
> match.
>
> In another, the organization defined in the POM does not match that used as
> the path to the artifact. Once again, ivy finds the file fine, but borks
> when doing a consistency check on the POM.
>
> Any help would be much appreciated.
>
> Thanks,
> Kevin
> --
> View this message in context: http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>
--
Gilles SCOKART