wayne, thanks a lot for your response, it helped to figure out what's going on.
it's indeed javac that aborts (yes aborts, no error, it just quits). something with annotations in enum constructors, it's not reported to the javac mailing list http://mail.openjdk.java.net/pipermail/compiler-dev/2013-July/006902.html i was wondering if maven could detect that javac does not end successfully, and then abort and blame the compilation directly instead of building an empty jar and going on, which takes longer to find the real issue. but then again i seem to be the only person affected by this ... i've found a workaround for my compilation, so for me the case is closed. thanks again! On Thu, Jul 25, 2013 at 3:45 AM, Wayne Fay <[email protected]> wrote: > > Any hint what to try next or an idea for a workaround much appreciated > > *sigh* > > In the future, sighs are unnecessary. > > > > The culprit is that the compilation puts nothing into the target folder, > > even though it says it compiles the 217 classes. No error whatsoever. > Maybe > > the words "Stale source detected" ring some bells? > > Can you please try "mvn -X compile" and then copy/paste the javac line > that Maven shows you to see if this works/compiles fine with javac or > not? If it works with javac with no issues, then we probably have a > Maven issue somewhere. But if javac doesn't like it, then you can't > really expect Maven to do much for you. > > You said it works in IntelliJ but this does not necessarily tell me > that it works in plain command-line javac. There are "lots" of things > that IDEs do to "help" people out. Please test that first. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
