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
anders.jacobs...@gmail.com wrote:
Hi!
The Jenkins Ivy plugin uses Ivy 2.1 internally so yes, it would not
allow version="2.2". Ivy 2.1 only allows "1.0", "1.1", "1.2", "1.3",
"1.4" and "2.0".
Good to know, but the manual doesn't say that the ivy-module version
tracks the release number.
The windows emailer kept insisting the mail was never sent.
Yikes.
Maarten Coene wrote:
Seems like a bug to me, could you provide more details?
Maarten
- Original Message
From: David Goblirsch
To: ivy-u...@ant.apache.org
Sent: Thu, February 25, 2010 7:18:33 PM
Subject: artifactreport leaves out some dependencies
I have a resolve target in an ant
Archie Cobbs wrote:
This is really an ant question, not an ivy question (I say that for
clarification, not to be annoying :-)
The simplest way would be to set some property "jar.published" in your jar
task (via ) and then make your publish task conditional on
this property being set (e.g., via )
it
do nothing with no changes, i.e., like javac, it does nothing if its
dependencies are up to date.
Thank you for your detailed response!
On Tue, Jan 20, 2009 at 2:31 PM, David Goblirsch <
dgoblir...@interactivebrokers.com> wrote:
If I have no changes to my source code or ivy.xml,
If I have no changes to my source code or ivy.xml, my build will do nothing
EXCEPT that the "publish" task still wants to push them to the local
repository.
In order to get the build to not fail, I have to set overwrite to "true".
My guess is I am missing something here. My "publish" task depen
