Maven errors are not reported

[fbricon]

Importing the attached example should override the default jdt settings (java 1.5) with the maven compiler configuration (java 1.8)

examples.zip

[fbricon]

@othomann so the problem is the pom.xml references a parent pom that can't be found. That causes m2e to be unable to read the pom, so no Maven project facade is configured, hence no configuration request is sent.

Actually, from command line, this is what you get:

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.mycompany.app:my-app:1.0: Could not find artifact org.jboss.tools.vscode:parent:pom:1.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) and 'parent.relativePath' points at wrong local POM @ line 5, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.mycompany.app:my-app:1.0 (/Users/fbricon/Downloads/examples/my-app/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.mycompany.app:my-app:1.0: Could not find artifact org.jboss.tools.vscode:parent:pom:1.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) and 'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

The bigger issue here is we're not reporting pom.xml issues back to the client. I need to check with @gorkem on how to proceed.

[gorkem]

Does m2e receive these errors ?

[fbricon]

Current WIP: some errors are not properly reported because of incomplete column index returned by m2e

I'm working on a fix for m2e: https://bugs.eclipse.org/bugs/show_bug.cgi?id=512825