Nothing wrong with using build helper... But *if* you have written a plugin to do your code generation, then the mojo that generates the source code should also add the generated source to the compile class path (projecthelper.addsources iirc)
For example I wrote a plugin to generate some code to help event logging, making a LogEvent class that had method signatures matching each event's requiered parameters... After the classes are generated in target/generated-sources/LogEvent/ I then add that path to the compile sources. HTH On Friday, 23 March 2012, Laird Nelson <ljnel...@gmail.com> wrote: > On Tue, Mar 20, 2012 at 7:05 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> if you are writing a plugin yourself, you can add the generated code >> to the compile classpath from your plugin itself once out of the >> hacking stage > > > Momentarily hijacking this--could you kindly point towards a doc somewhere > that shows how to do this? I have been using the build helper plugin even > when NOT hacking; I'd love to know the proper Maven Way here. > > Best, > Laird > > -- > http://about.me/lairdnelson >
