Ah, thanks Steve. When I looked a while back, it looked like it was failing
with the same Jetty compile issues as we were seeing in the Jetty 9 upgrade
issue.

- Mark

On Tue Jan 13 2015 at 12:48:56 PM Steve Rowe <[email protected]> wrote:

> Maven doesn’t use the .ivy caches.
>
> I’m looking into the problem, and I’ve traced it to something to do with
> moving example/ivy.xml to server/ivy.xml - these are used to build the
> dependencies sections in the Maven POMs.
>
> Steve
>
> > On Jan 13, 2015, at 12:41 PM, Mark Miller <[email protected]> wrote:
> >
> > I don't currently have the ability to log into these 3 jenkins machines.
> Can someone that does please nuke the .ivy caches? See SOLR-4839.
> >
> > On Mon Jan 12 2015 at 1:44:18 PM Apache Jenkins Server <
> [email protected]> wrote:
> > Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1319/
> >
> > No tests ran.
> >
> > Build Log:
> > [...truncated 39089 lines...]
> >       [mvn] [INFO] ------------------------------
> -------------------------------
> >       [mvn] [INFO] ------------------------------
> -------------------------------
> >       [mvn] [ERROR] COMPILATION ERROR :
> >       [mvn] [INFO] ------------------------------
> -------------------------------
> >
> > [...truncated 696 lines...]
> > BUILD FAILED
> > /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:542:
> The following error occurred while executing this line:
> > /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:204:
> The following error occurred while executing this line:
> > : Java returned: 1
> >
> > Total time: 20 minutes 1 second
> > Build step 'Invoke Ant' marked build as failure
> > Email was triggered for: Failure
> > Sending email for trigger: Failure
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to