demobox, any chance you could reach out to the CloudBees guys and see if they can figure out why we keep having build failures like this one and the others with Maven repo issues?
A. On Thu, Jan 2, 2014 at 1:02 PM, <[email protected]> wrote: > See <https://jclouds.ci.cloudbees.com/job/jclouds-karaf-1.5.x-branch/98/> > > ------------------------------------------ > Started by an SCM change > Building remotely on b8cce115 in workspace < > https://jclouds.ci.cloudbees.com/job/jclouds-karaf-1.5.x-branch/ws/> > Checkout:jclouds-karaf-1.5.x-branch / < > https://jclouds.ci.cloudbees.com/job/jclouds-karaf-1.5.x-branch/ws/> - > hudson.remoting.Channel@33f64971:b8cce115 > Using strategy: Default > Last Built Revision: Revision ece3c6842011d76756e232df3c6385a9f03c0daf > (origin/1.5.x) > Cloning the remote Git repository > Cloning repository > https://git-wip-us.apache.org/repos/asf/jclouds-karaf.git > git --version > git version 1.7.11.7 > Fetching upstream changes from origin > Commencing build of Revision ece3c6842011d76756e232df3c6385a9f03c0daf > (origin/1.5.x) > Checking out Revision ece3c6842011d76756e232df3c6385a9f03c0daf > (origin/1.5.x) > Parsing POMs > ERROR: No such settings file /private/jclouds/settings.xml exists > Please verify that your alternate settings file is specified properly and > exists in the workspace. > >
