Kent, if I may turn the tables--assuming you get past this NullPointerException, what would be your sales pitch to someone like me who has not yet adopted the Jenkins Ivy plugin?
On Wed, Feb 23, 2011 at 10:41 AM, Kent Rosenkoetter < krosenkoet...@cequint.com> wrote: > I have not been able to find any ivy.xml file in the wild that works with > Jenkins+Ivy. In fact, I just created a new empty project and put the > following minimal ivy.xml file into it, and still got the same > NullPointerException. > > <?xml version="1.0" encoding="UTF-8"?> > <ivy-module version="2.2" xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation=" > http://ant.apache.org/ivy/schemas/ivy.xsd";> > <info module="IvyTestProject" organisation="com.cequint"> > </info> > </ivy-module> > > If that fails, I don't know how anybody is using this successfully. > > -Kent > > -----Original Message----- > From: Mitch Gitman [mailto:mgit...@gmail.com] > Sent: Wednesday, February 23, 2011 10:10 AM > To: ivy-user@ant.apache.org > Subject: Re: Error parsing ivy.xml files using Jenkins > > 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. > >
