ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: Error parsing ivy.xml files using Jenkins
Date Wed, 23 Feb 2011 18:09:56 GMT
If your desire is just to get things working and not to fix the plugin
itself (whether or not there's anything worth fixing), then we're down to
standard developer troubleshooting techniques. I would recommend tracking
down an existing ivy.xml out in the wild that you know works against the
Jenkins plugin. Use that as a template for your own least dependent
project's ivy.xml and proceed to adapt it to your project's specifics. I
recall there are a few things that are somewhat unorthodox, but not wrong,
about your ivy.xml.

It sounds like your interest in using the Jenkins plugin strictly revolves
around establishing the jobs' build order.

On Wed, Feb 23, 2011 at 9:45 AM, Kent Rosenkoetter <> wrote:

> The one I just posted is for our base module that does not depend on any
> other in-house modules.  It only depends on common libraries like junit.
>  That is the one I tried to make Jenkins+Ivy build solo, and failed with the
> stack trace I just sent out.
> So Ivy is throwing the exception on the simplest possible ivy.xml I can
> provide, with or without the revision included.
> -Kent
> -----Original Message-----
> From: Mitch Gitman []
> Sent: Wednesday, February 23, 2011 8:12 AM
> To:
> Subject: Re: Error parsing ivy.xml files using Jenkins
> For lack of anyone more knowledgeable about the Jenkins Ivy plugin stepping
> forward, let me throw out a couple more ideas.
> Since the ivy.xml that Ivy really cares about when it's resolving is the
> one
> that resides on Nexus, you should share one from an in-house project that's
> a common dependency to see if anyone can spot any obvious problems. (I'm
> presuming here that you're using Nexus as an Ivy repository and publishing
> the ivy.xml rather than publishing POMs.)
> Try paring things down to the simplest possible case. Have the plugin
> manage
> no projects other than the one that is the least dependent. See if that
> works. If it does, keep adding each dependent project until it stops
> working. That would at least isolate where the problem is arising.
> Question. Are you hoping to accomplish anything with the Jenkins plugin
> beyond automatically ordering your jobs?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message