Why is there a preReq for the maven-jalopy-plugin to perform a java:compile before running jalopy on the source files?
I find this annoying when attempting to debug stuff. As the line numbers are all off in this situation. The project I'm working on has many, many, many (did I say many yet?) generated source files. The process (in straight ant) that works for us is ... 1) get latest xml definition of old legacy socket protocol. 2) perform xslt transform against legacy.xml to generate optimum java source to read/write against protocol. 3) perform xslt transform against legacy.xml to generate some integration tests for the protocol to ensure that the spec and reality mesh. 3) jalopy the source to make source readable. 4) compile sources. 5) test. Now, if we use the maven with the maven-jalopy-plugin step #4 moves up to between #1 and #2. If we have to debug the code, then the line numbers in the compiled classes do not match the line numbers in the source files. Which is annoying to say the least. Can we either make the java:compile prereq optional or remove it entirely? /* Joakim Erdfelt */
