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 David Goblirsch <dg...@interactivebrokers.com> on 2012/04/02 22:21:00 UTC
How do I change the default conflict manager?
How can I change the default conflict manager from
latest-revision
to
latest-compatible?
I work at a site where we have 300+ ivy projects, and every time
I put out a new 3rd party jar the builds all break unless I start at
the bottom of the dependency hierarchy and rebuild everything. Updating
to Spring 3.1 from 3.0, Hibernate 3.6.5 from 3.6.4, etc. causes failures
unless trigger a monster rebuild from the lowest-level projects.
I am unable to find in the documentation the magic system property,
if any, that allows me to do this by default instead of requiring that
all of the projects do it individually (yuck).
I saw Archie Cobb's posts; I am not asking that the default ivy
out-of-the-box
be changed. I just want a magic incantation for my site in the master
settings
file. We do not use version numbers on most of our internal jars, and
we do not produce jars for outside use.
Thanks.
Re: How do I change the default conflict manager?
Posted by Maarten Coene <ma...@yahoo.com>.
Can you create a new JIRA issue for this?
If you can please attach a reproducible test case to the issue.
Maarten
________________________________
From: David Goblirsch <dg...@interactivebrokers.com>
To: ivy-user@ant.apache.org
Sent: Monday, April 2, 2012 11:35 PM
Subject: Re: How do I change the default conflict manager?
Maarten Coene wrote:
> Please try again with latest trunk build.
> We made some changes to this conflict manager recently.
>
> Maarten
>
>
using version of 2012-04-01 produces
same NPE stacktrace except that the first line changes the line number to 263:
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:263)
remaining lines are the same.
>
> ________________________________
> From: David Goblirsch <dg...@interactivebrokers.com>
> To: ivy-user@ant.apache.org Sent: Monday, April 2, 2012 11:24 PM
> Subject: Re: How do I change the default conflict manager?
> David Goblirsch wrote:
>
>> Tom McGlynn wrote:
>>
>>> In ivysettings.xml:
>>>
>>> <settings defaultConflictManager="lastest-compatible" />
>>>
>>> On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
>>> dgoblirsch@interactivebrokers.com> wrote:
>>>
>>>
>> thank you so much.
>>
>
> Except now I get NPE. I made no changes to any file expect
> for the one change you suggested in the master settings file. That is the
> only difference.
>
> I am using the 2.2.1 alpha build from 2012-03-13.
>
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:264)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCallerAndRestartResolveIfPossible(LatestCompatibleConflictManager.java:190)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleIncompatibleConflict(LatestCompatibleConflictManager.java:166)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.resolveConflicts(LatestCompatibleConflictManager.java:114)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflicts(ResolveEngine.java:1018)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:895)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:945)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:833)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:692)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:575)
> at org.apache.ivy.ant.IvyArtifactReport.doExecute(IvyArtifactReport.java:94)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
Re: How do I change the default conflict manager?
Posted by David Goblirsch <dg...@interactivebrokers.com>.
Maarten Coene wrote:
> Please try again with latest trunk build.
> We made some changes to this conflict manager recently.
>
> Maarten
>
>
using version of 2012-04-01 produces
same NPE stacktrace except that the first line changes the line number
to 263:
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:263)
remaining lines are the same.
>
> ________________________________
> From: David Goblirsch <dg...@interactivebrokers.com>
> To: ivy-user@ant.apache.org
> Sent: Monday, April 2, 2012 11:24 PM
> Subject: Re: How do I change the default conflict manager?
>
> David Goblirsch wrote:
>
>> Tom McGlynn wrote:
>>
>>> In ivysettings.xml:
>>>
>>> <settings defaultConflictManager="lastest-compatible" />
>>>
>>> On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
>>> dgoblirsch@interactivebrokers.com> wrote:
>>>
>>>
>>>
>> thank you so much.
>>
>
> Except now I get NPE. I made no changes to any file expect
> for the one change you suggested in the master settings file. That is the
> only difference.
>
> I am using the 2.2.1 alpha build from 2012-03-13.
>
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:264)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCallerAndRestartResolveIfPossible(LatestCompatibleConflictManager.java:190)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleIncompatibleConflict(LatestCompatibleConflictManager.java:166)
> at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.resolveConflicts(LatestCompatibleConflictManager.java:114)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflicts(ResolveEngine.java:1018)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:895)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:945)
> at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:833)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:692)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
> at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:575)
> at org.apache.ivy.ant.IvyArtifactReport.doExecute(IvyArtifactReport.java:94)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
Re: How do I change the default conflict manager?
Posted by Maarten Coene <ma...@yahoo.com>.
Please try again with latest trunk build.
We made some changes to this conflict manager recently.
Maarten
________________________________
From: David Goblirsch <dg...@interactivebrokers.com>
To: ivy-user@ant.apache.org
Sent: Monday, April 2, 2012 11:24 PM
Subject: Re: How do I change the default conflict manager?
David Goblirsch wrote:
> Tom McGlynn wrote:
>> In ivysettings.xml:
>>
>> <settings defaultConflictManager="lastest-compatible" />
>>
>> On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
>> dgoblirsch@interactivebrokers.com> wrote:
>>
>>
>
> thank you so much.
Except now I get NPE. I made no changes to any file expect
for the one change you suggested in the master settings file. That is the
only difference.
I am using the 2.2.1 alpha build from 2012-03-13.
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:264)
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCallerAndRestartResolveIfPossible(LatestCompatibleConflictManager.java:190)
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleIncompatibleConflict(LatestCompatibleConflictManager.java:166)
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.resolveConflicts(LatestCompatibleConflictManager.java:114)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflicts(ResolveEngine.java:1018)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:895)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:945)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:833)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:692)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:575)
at org.apache.ivy.ant.IvyArtifactReport.doExecute(IvyArtifactReport.java:94)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Re: How do I change the default conflict manager?
Posted by David Goblirsch <dg...@interactivebrokers.com>.
David Goblirsch wrote:
> Tom McGlynn wrote:
>> In ivysettings.xml:
>>
>> <settings defaultConflictManager="lastest-compatible" />
>>
>> On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
>> dgoblirsch@interactivebrokers.com> wrote:
>>
>>
>
> thank you so much.
Except now I get NPE. I made no changes to any file expect
for the one change you suggested in the master settings file. That is the
only difference.
I am using the 2.2.1 alpha build from 2012-03-13.
at
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCaller(LatestCompatibleConflictManager.java:264)
at
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.blackListIncompatibleCallerAndRestartResolveIfPossible(LatestCompatibleConflictManager.java:190)
at
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleIncompatibleConflict(LatestCompatibleConflictManager.java:166)
at
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.resolveConflicts(LatestCompatibleConflictManager.java:114)
at
org.apache.ivy.core.resolve.ResolveEngine.resolveConflicts(ResolveEngine.java:1018)
at
org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:895)
at
org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:945)
at
org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:833)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:692)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at
org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at
org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:575)
at
org.apache.ivy.ant.IvyArtifactReport.doExecute(IvyArtifactReport.java:94)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Re: How do I change the default conflict manager?
Posted by David Goblirsch <dg...@interactivebrokers.com>.
Tom McGlynn wrote:
> In ivysettings.xml:
>
> <settings defaultConflictManager="lastest-compatible" />
>
> On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
> dgoblirsch@interactivebrokers.com> wrote:
>
>
thank you so much.
>> How can I change the default conflict manager from
>>
>> latest-revision
>>
>> to
>>
>> latest-compatible?
>>
>> I work at a site where we have 300+ ivy projects, and every time
>> I put out a new 3rd party jar the builds all break unless I start at
>> the bottom of the dependency hierarchy and rebuild everything. Updating
>> to Spring 3.1 from 3.0, Hibernate 3.6.5 from 3.6.4, etc. causes failures
>> unless trigger a monster rebuild from the lowest-level projects.
>>
>> I am unable to find in the documentation the magic system property,
>> if any, that allows me to do this by default instead of requiring that
>> all of the projects do it individually (yuck).
>>
>> I saw Archie Cobb's posts; I am not asking that the default ivy
>> out-of-the-box
>> be changed. I just want a magic incantation for my site in the master
>> settings
>> file. We do not use version numbers on most of our internal jars, and
>> we do not produce jars for outside use.
>>
>> Thanks.
>>
>>
>>
>>
>
>
Re: How do I change the default conflict manager?
Posted by Tom McGlynn <tm...@ieee.org>.
In ivysettings.xml:
<settings defaultConflictManager="lastest-compatible" />
On Mon, Apr 2, 2012 at 4:21 PM, David Goblirsch <
dgoblirsch@interactivebrokers.com> wrote:
> How can I change the default conflict manager from
>
> latest-revision
>
> to
>
> latest-compatible?
>
> I work at a site where we have 300+ ivy projects, and every time
> I put out a new 3rd party jar the builds all break unless I start at
> the bottom of the dependency hierarchy and rebuild everything. Updating
> to Spring 3.1 from 3.0, Hibernate 3.6.5 from 3.6.4, etc. causes failures
> unless trigger a monster rebuild from the lowest-level projects.
>
> I am unable to find in the documentation the magic system property,
> if any, that allows me to do this by default instead of requiring that
> all of the projects do it individually (yuck).
>
> I saw Archie Cobb's posts; I am not asking that the default ivy
> out-of-the-box
> be changed. I just want a magic incantation for my site in the master
> settings
> file. We do not use version numbers on most of our internal jars, and
> we do not produce jars for outside use.
>
> Thanks.
>
>
>