I've tried both refresh and maven->update project but to no avail. Steven
On Thu, May 5, 2016 at 2:09 PM, Yingyi Bu <buyin...@gmail.com> wrote: > Eclipse errors don't necessarily mean that the binaries are missing, > sometimes it doesn't update errors in time. > I'm guessing that you might have "cleaned" the workspace after you do "mvn > clean; mvn package -DskipTests". > > The following could be relevant: > I have added a bytecode generation maven plugin recently, thus "clean" > from Eclipse will remove all the generated classes, > which can cause class-not-found-errors at instance startup time. > "Refresh" should be fine. > > Best, > Yingyi > > > On Thu, May 5, 2016 at 2:00 PM, Steven Jacobs <sjaco...@ucr.edu> wrote: > >> It is unable to even start running the tests, as it considers the files >> to have errors. See attached >> Steven >> >> On Thu, May 5, 2016 at 1:51 PM, Yingyi Bu <buyin...@gmail.com> wrote: >> >>> Can you paste the error stack trace (from the Eclipse console) by >>> re-running one particular failed test? >>> >>> Best, >>> Yingyi >>> >>> On Thu, May 5, 2016 at 1:49 PM, Steven Jacobs <sjaco...@ucr.edu> wrote: >>> >>> > Yes. The command line maven build (including clean) works fine. I've >>> tried >>> > refreshing everything in Eclipse as well. >>> > Steven >>> > >>> > On Thu, May 5, 2016 at 1:43 PM, Yingyi Bu <buyin...@gmail.com> wrote: >>> > >>> > > Did you build in maven command line first and then run in eclipse? >>> > > >>> > > Best, >>> > > Yingyi >>> > > >>> > > On Thu, May 5, 2016 at 1:37 PM, Steven Jacobs <sjaco...@ucr.edu> >>> wrote: >>> > > >>> > > > Is anyone else having issues with running the latest Master in >>> > Eclipse? I >>> > > > get a few different strange errors, the strangest of which comes >>> from >>> > the >>> > > > servlets (e.g. RESTAPIServlet) and complains about the way that >>> errors >>> > > are >>> > > > being thrown. >>> > > > Steven >>> > > > >>> > > >>> > >>> >> >> >
