I've just received this same error deploying WSO2 Identity Server with Java 1.8. I searched around and found your post. What little evidence I can find on the internet suggests it to be general 1.8 wonkiness.
On Monday, April 7, 2014 9:10:42 AM UTC-5, fabrizio.giudici wrote: > > Hello. > > I've started porting some of my pet projects to JDK 8. Most of them use > Spring and AspectJ, so I did expect some problems related with bytecode > manipulation (as it happened at the beginning with JDK 7). Indeed, no > problems at the first smoke tests (with AspectJ 1.8.0.RC2) even though > there has been a sort of "retarded flame" - inconsistent and random > errors. I suppose I'll have to wait for the final AspectJ 1.8.0. > > But this wasn't my goal for this post. I've also configured my Hudson so > all the other projects (still running with -source 1.7 and -target 1.7) > are also compiled with the JDK 8 in "7 mode". I've found a strange error > with AspectJ failing with a curious > > The type java.lang.CharSequence cannot be resolved. It is > indirectly > referenced from required .class files > > > Did some of you already made some experience with compiling with JDK 8? > Sure I wouldn't consider it mature for production until no problems appear > > for several weeks, but I didn't expect to see existing projects break > without any change. > > -- > Fabrizio Giudici - Java Architect @ Tidalwave s.a.s. > "We make Java work. Everywhere." > http://tidalwave.it/fabrizio/blog - [email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/d/optout.
