That works - thank you, Fred!
On Wed, Dec 4, 2019 at 12:56 PM Fred Bricon wrote:
> The culprit is hubspot-javac
> m2e doesn't know anything about this compiler, so doesn't configure JDT
> accordingly.
>
> You need to add the following to your (parent) pom.xml:
>
> ...
>
>
>
> org.eclipse.m2e
The culprit is hubspot-javac
m2e doesn't know anything about this compiler, so doesn't configure JDT
accordingly.
You need to add the following to your (parent) pom.xml:
...
org.eclipse.m2e
lifecycle-mapping
1.0.0
org.apache.maven.plugins
maven-compiler-plugin
[3.0,)
compile
testCompile
Here are the 2 sections tagged maven-compiler-plugin:
https://gist.github.com/wsorenson/e61e3ad60a0755ae8525b588d3a59551
On Wed, Dec 4, 2019 at 12:26 PM Fred Bricon wrote:
> The Java nature is added automatically and the Java configuration done
> according to the maven-compiler-plugin config
The Java nature is added automatically and the Java configuration done
according to the maven-compiler-plugin configuration.
Can you share the content of you maven-compiler-plugin config, from
running mvn help:effective-pom?
On Wed, Dec 4, 2019 at 6:19 PM Whitney Sorenson
wrote:
> Hello,
>
> I'v
Hello,
I've been using m2e successfully for many years and I am abruptly running
into an issue where m2e no longer recognizes imported maven projects as
Java projects and thus doesn't add the Java nature.
I tried a new workspace, new version of Eclipse (2019-09) and the problem
has persisted.
Pe
