to me, projects that have their own annotation processors are a bit corner-case. We should have a documented approach for that situation for sure. To me the workaround with resource:copy goal that copies the META-INF/services/xxx entry *after* compilation sounds like the best solution.
Milos On Tue, Mar 30, 2010 at 11:03 AM, Mark Hobson <[email protected]> wrote: > On 29 March 2010 10:35, Milos Kleint <[email protected]> wrote: > > yes, one place when this issue arises is when your own project defines a > > annotation processor of it's own. See > > http://jira.codehaus.org/browse/MCOMPILER-97 > > Hmm, maybe we'll have to split the compiler plugin up into two > different executions for proc:none and proc:only. It'd be interesting > to see what the actual performance hit is for this set up compared to > a single invocation. > > > I'd like to do a 2.2 release sometimes later this month. > > Cool, I'll try it out soon. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
