You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Vladimir Ivanov <le...@gmail.com> on 2012/07/04 16:50:08 UTC
Re: Build failed in Jenkins: ESME #867
Hi guys,
Please see my comments for https://issues.apache.org/jira/browse/ESME-360
issue.
Vladimir
2012/3/4 Ethan Jewett <es...@gmail.com>
> Hi all,
>
> So, there was no obvious improvement in the rate of test failures, so I did
> some work on this today and I think I've fixed the problem. What the
> problem was, I cannot say exactly. It seems that there might have been an
> API change in the location of WebAppContext in the org.mortbay.jetty
> package, so I've locked the version in to 6.1.22, which seems to work. I
> believe that the issue was around the version of the plugin, but I'm not
> sure. I also added explicit versions to most plugins in the pom.xml to get
> rid of the scary maven warning messages.
>
> I had to make similar changes for SBT in order to get rid of the error
> there.
>
> We seem to have some test failures now, so that would be the next thing to
> look in to. There are also a large number of deprecation warnings that we
> should address. I'm looking forward to being able to spend more significant
> amounts of time on ESME starting in May, so hopefully I can start to drive
> the cleanup as well as some of the larger projects (Akka/Camel integration)
> we have planned in May/June.
>
> I've turned on email notifications in Jenkins (builds.apache.org) again.
>
> Cheers,
> Ethan
>
> On Wed, Feb 22, 2012 at 2:29 PM, Richard Hirsch <hirsch.dick@gmail.com
> >wrote:
>
> > Thanks.
> >
> > I'll check back next week.
> >
> > R.
> >
> > On Wed, Feb 22, 2012 at 1:15 PM, Ethan Jewett <es...@gmail.com>
> wrote:
> > > 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 <es...@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
> > >>> <je...@builds.apache.org> wrote:
> > >>> > error: WebAppContext is not a member of org.mortbay.jetty.webapp
> > >>> > [WARNING] import org.mortbay.jetty.webapp.WebAppContext
> > >>>
> > >>
> > >>
> >
>
--
Best Regards,
Vladimir Ivanov
Re: Build failed in Jenkins: ESME #867
Posted by Vladimir Ivanov <le...@gmail.com>.
Yep, XMPP Producer is Akka actor.
2012/7/4 Richard Hirsch <hi...@gmail.com>
> @Vladimir
>
> Welcome back.
>
> Great to see that you are looking at the akka integration.
>
> Is the XMPP Producer component integration based on akka?
>
> D.
>
>
>
> On Wed, Jul 4, 2012 at 4:50 PM, Vladimir Ivanov <le...@gmail.com>
> wrote:
> > Hi guys,
> >
> > Please see my comments for
> https://issues.apache.org/jira/browse/ESME-360
> > issue.
> >
> > Vladimir
> >
> > 2012/3/4 Ethan Jewett <es...@gmail.com>
> >
> >> Hi all,
> >>
> >> So, there was no obvious improvement in the rate of test failures, so I
> did
> >> some work on this today and I think I've fixed the problem. What the
> >> problem was, I cannot say exactly. It seems that there might have been
> an
> >> API change in the location of WebAppContext in the org.mortbay.jetty
> >> package, so I've locked the version in to 6.1.22, which seems to work. I
> >> believe that the issue was around the version of the plugin, but I'm not
> >> sure. I also added explicit versions to most plugins in the pom.xml to
> get
> >> rid of the scary maven warning messages.
> >>
> >> I had to make similar changes for SBT in order to get rid of the error
> >> there.
> >>
> >> We seem to have some test failures now, so that would be the next thing
> to
> >> look in to. There are also a large number of deprecation warnings that
> we
> >> should address. I'm looking forward to being able to spend more
> significant
> >> amounts of time on ESME starting in May, so hopefully I can start to
> drive
> >> the cleanup as well as some of the larger projects (Akka/Camel
> integration)
> >> we have planned in May/June.
> >>
> >> I've turned on email notifications in Jenkins (builds.apache.org)
> again.
> >>
> >> Cheers,
> >> Ethan
> >>
> >> On Wed, Feb 22, 2012 at 2:29 PM, Richard Hirsch <hirsch.dick@gmail.com
> >> >wrote:
> >>
> >> > Thanks.
> >> >
> >> > I'll check back next week.
> >> >
> >> > R.
> >> >
> >> > On Wed, Feb 22, 2012 at 1:15 PM, Ethan Jewett <es...@gmail.com>
> >> wrote:
> >> > > 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 <es...@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
> >> > >>> <je...@builds.apache.org> wrote:
> >> > >>> > error: WebAppContext is not a member of org.mortbay.jetty.webapp
> >> > >>> > [WARNING] import org.mortbay.jetty.webapp.WebAppContext
> >> > >>>
> >> > >>
> >> > >>
> >> >
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Vladimir Ivanov
>
--
Best Regards,
Vladimir Ivanov
Re: Build failed in Jenkins: ESME #867
Posted by Richard Hirsch <hi...@gmail.com>.
@Vladimir
Welcome back.
Great to see that you are looking at the akka integration.
Is the XMPP Producer component integration based on akka?
D.
On Wed, Jul 4, 2012 at 4:50 PM, Vladimir Ivanov <le...@gmail.com> wrote:
> Hi guys,
>
> Please see my comments for https://issues.apache.org/jira/browse/ESME-360
> issue.
>
> Vladimir
>
> 2012/3/4 Ethan Jewett <es...@gmail.com>
>
>> Hi all,
>>
>> So, there was no obvious improvement in the rate of test failures, so I did
>> some work on this today and I think I've fixed the problem. What the
>> problem was, I cannot say exactly. It seems that there might have been an
>> API change in the location of WebAppContext in the org.mortbay.jetty
>> package, so I've locked the version in to 6.1.22, which seems to work. I
>> believe that the issue was around the version of the plugin, but I'm not
>> sure. I also added explicit versions to most plugins in the pom.xml to get
>> rid of the scary maven warning messages.
>>
>> I had to make similar changes for SBT in order to get rid of the error
>> there.
>>
>> We seem to have some test failures now, so that would be the next thing to
>> look in to. There are also a large number of deprecation warnings that we
>> should address. I'm looking forward to being able to spend more significant
>> amounts of time on ESME starting in May, so hopefully I can start to drive
>> the cleanup as well as some of the larger projects (Akka/Camel integration)
>> we have planned in May/June.
>>
>> I've turned on email notifications in Jenkins (builds.apache.org) again.
>>
>> Cheers,
>> Ethan
>>
>> On Wed, Feb 22, 2012 at 2:29 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>>
>> > Thanks.
>> >
>> > I'll check back next week.
>> >
>> > R.
>> >
>> > On Wed, Feb 22, 2012 at 1:15 PM, Ethan Jewett <es...@gmail.com>
>> wrote:
>> > > 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 <es...@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
>> > >>> <je...@builds.apache.org> wrote:
>> > >>> > error: WebAppContext is not a member of org.mortbay.jetty.webapp
>> > >>> > [WARNING] import org.mortbay.jetty.webapp.WebAppContext
>> > >>>
>> > >>
>> > >>
>> >
>>
>
>
>
> --
> Best Regards,
> Vladimir Ivanov