<div dir="ltr">I agree with George. I think that parser-java is probably the right place for this. The command should be active if there is a current project, and JavaCompilerFacet is enabled in that project. The command is build-system agnostic, so it shouldn't go in maven. I think parser-java is the only place for it.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 6, 2014 at 1:24 PM, George Gastaldi <span dir="ltr"><<a href="mailto:ggastald@redhat.com" target="_blank">ggastald@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why not adding to parser-java? That seems the best place to be, since JavaCompilerFacet is in there<br>
<br>
> Em 06/04/2014, ās 14:14, "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>> escreveu:<br>
<div class="HOEnZb"><div class="h5">><br>
> Hi guys!<br>
><br>
> I was wondering where to put the compiler version UI command. it has dependency to parser-java (because of the Facet), so it can't go to the projects addon. Otherwise it would introduce a circular dependency. I am not really happy about adding the command to the parser-java addon either.<br>
><br>
> I looked at all the addons that have dependency to parser-java, but couldn't find any suitable (dev-tools, addons, scaffold, javaee, database-tools).<br>
><br>
> What would you recommend here?<br>
><br>
> Thanks,<br>
> Ivan<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>