I have noticed a small (but annoying) issue wrt Gmaven.
If one of the Groovy classes has the following structure:
/** * some info */ package foo /* * some other info */ public class A { }
We get a 'syntax error @[9,1] in UNKNOWN SOURCE' message during 'mvn install' (see complete message under [1]). IMO, it should not be possible to crash Gmaven with exotic comments (although it's not usual to have javadoc comments before the package def and non-javadoc ones before the class). Plus the error message should at least mention the source file where the error occured.
Any thoughts?
Cheers, Patrick
P.S. Test project in attachment. Just unpack and run 'mvn install'.
[1] Complete stack trace
$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Unnamed - GmavenTest:GmavenTestC:jar:0.0.1-SNAPSHOT [INFO] task-segment: [install] [INFO] ------------------------------------------------------------------------ [INFO] [groovy:generateStubs {execution: gmaven-generateStubs}] [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] syntax error @[9,1] in UNKNOWN SOURCE