Hmm,<br><br>Good questions. I think #2 would probably be the easiest, but we could offer #1 as an alternative for those who don't want to use the maven build plugin.<br><br>I think #3 would probably be the most robust for future use. What kinds of methods are you thinking of including for the facet?<br>
<br>~Lincoln<br><br><div class="gmail_quote">On Sun, Jul 3, 2011 at 3:41 PM, Ken Finnigan <span dir="ltr"><<a href="mailto:ken@kenfinnigan.me">ken@kenfinnigan.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hey Lincoln,<br><br>Have been working on adding JPA model generation to the persistence plugin over the last few days and have been mulling over the best way to implement it and wanted to get your thoughts.<br><br>I see that there are a few possibilities:<br>
<br>1) Call the NativeMethodExec utility to call javac for running annotation processing only.<br>2) Add an annotation processing profile to the pom as part of the install of the plugin (if they select they want model gen), and then performing the model gen would execute the maven to process and generate annotations<br>
3) An extension of 2 would be to make an AnnotationProcessorFacet, and then do 2 as a Maven implementation of that facet.<br><br>After thinking about it today I think 3 seems the most flexible, but wanted to get your thoughts.<br>
<br>Thanks<br><font color="#888888">Ken<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>