Restrict lifecycle-mapping to trigger the ClasspathConfigurator only for compilerIds "eclipse" or "jdt" #12
Comments
|
@kwin sorry I'm only seeing & reacting to this now! Would you be willing to raise a PR for this? |
vorburger
added a commit
to vorburger/eclipse-external-annotations-m2e-plugin
that referenced
this issue
Sep 16, 2017
Trigger the ClasspathConfigurator only for "eclipse" or "jdt" compiler. Otherwise running the extension is just unnecessary overhead. Similar to https://github.com/jbosstools/m2e-jdt-compiler/blob/master/org.jboss.tools.m2e.jdt.core/lifecycle-mapping-metadata.xml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to https://github.com/jbosstools/m2e-jdt-compiler/blob/master/org.jboss.tools.m2e.jdt.core/lifecycle-mapping-metadata.xml the execution of this extension should be restricted to the
compilerIdeclipseorjdt. Otherwise running the extension is just unnecessary overhead.The text was updated successfully, but these errors were encountered: