esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <esjew...@gmail.com>
Subject Re: Build failed in Jenkins: ESME #867
Date Wed, 22 Feb 2012 12:15:54 GMT
I've turned off email notifications on Hudson for the time being.

Cheers,
Ethan

On Mon, Feb 20, 2012 at 6:21 PM, Ethan Jewett <esjewett@gmail.com> wrote:

> Certainly seems that something changed. I'm wondering if this earlier
> warning has something to do with the later error:
>
> [WARNING] Could not transfer metadata org.mortbay.jetty:jetty/maven-metadata.xml
> from/to Apache Repo (
> http://people.apache.org/repo/m1-ibiblio-rsync-repository): No connector
> available to access repository Apache Repo (
> http://people.apache.org/repo/m1-ibiblio-rsync-repository) of type legacy
> using the available factories WagonRepositoryConnectorFactory
>
> I just tried a completely clean build locally after deleting my .m2
> repository and it seems to have worked fine. Maybe we need to send this
> error to Apache infrastructure?
>
> Ethan
>
>
> On Mon, Feb 20, 2012 at 4:15 PM, Richard Hirsch <hirsch.dick@gmail.com>wrote:
>
>> Is this error coming from a change in jetty?
>>
>>  error: WebAppContext is not a member of org.mortbay.jetty.webapp
>> [WARNING] import org.mortbay.jetty.webapp.WebAppContext
>>
>> D.
>>
>> On Mon, Feb 20, 2012 at 1:17 PM, Apache Jenkins Server
>> <jenkins@builds.apache.org> wrote:
>> > error: WebAppContext is not a member of org.mortbay.jetty.webapp
>> > [WARNING] import org.mortbay.jetty.webapp.WebAppContext
>>
>
>

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