Hello Mark, On Mon, Mar 29, 2010 at 10:39 AM, Mark Hobson <markhob...@gmail.com> wrote:
<snip> > >> Obviously this is complicated if we're also compiling too. > > > > Yes, you would have to somehow recognize this upfront and pass -proc:none > to > > avoid processing? but how do you figure? > > > > the current netbeans annotations do generate resources (layer.xml files > and > > META-INF/services content) and also java/class files. If you generate > class > > files, you cannot probably do just annotation processing (in > > process-resources) without compiling as well. Or we would have to add > the > > generated sources root to the project? > > OTOH when resources get generated in compile phase, it probably only > matters > > if you want to do filtering of these resources? but that assumes your > > annotations do generated filterable content. Hmm. I suppose this setup > can > > be configured in the pom, additional execution with -proc:only and the > > default compile execution with -proc:none > > > > So I would go with doing annotation processing along with compiling, it's > > going to be faster and is actually the default javac behaviour as well. > The > > other scenarios seem to be configurable then as well using the current > > parameters, right? > > Sounds good to me. I just wanted to highlight the fact that this > circumnavigates Maven's traditional lifecycle phases. > 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 > > Thanks for doing the work on this, I'll look forward to using it soon! > > I'd like to do a 2.2 release sometimes later this month. > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
