Any sort of missing class really should be a compile time exception, which I think means you must have stale class files *somewhere*. You could try doing a find checkout -name "*.class" just as a sanity check. Also, it's possible something in your local maven repo is somehow coming into play, maybe blow that away and rebuild it and/or do an mvn install to be sure that remove dependencies aren't out of sync with local code?
--Rafael On Mon, Jul 6, 2015 at 11:02 AM, Gordon Sim <[email protected]> wrote: > On 07/06/2015 02:23 PM, Robbie Gemmell wrote: > >> On 6 July 2015 at 14:17, Gordon Sim <[email protected]> wrote: >> >>> On 07/06/2015 01:24 PM, Rafael Schloming wrote: >>> >>>> >>>> Can you try doing an mvn clean and seeing if it is still an issue? >>>> >>> >>> >>> I see the same thing after mvn clean >>> >>> >> Does cleaning the checkout as a whole make any difference? >> > > Doesn't seem to, no. > > > To preview what woudl be deleted: >> git clean -n -d -x -e "*.classpath" -e "*.project" -e "*.settings" . >> >> To actually delete things: >> git clean -f -d -x -e "*.classpath" -e "*.project" -e "*.settings" . >> >> The -e flags are protecting project files generated by Eclipse...if >> you dont use it, no need for them. >> >> >
