In the past, when something does modification to the classes other than the
javac process, I had been putting the modified classes in another location
that is higher on the classpath to avoid this problem. The largest example
of this is with instrumentation from Cobertura, or some other coverage
tool. In that case, the main motivation was because I didn't want the
instrumented classes to end up in the war.
Would this type of an approach be more appropriate for your binary
modification of the classes?
I'm afraid not. I'm writing a plugin for general consumption that users
might want to hook into their workflow as they see fit. I really have to
provide a way to keep the sources and any created artifacts in sync. But
thanks for your answer. Much appreciated.
Cheers,
Marco
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
