Eclipse Community Forums: Maven Integration (M2E) » m2e forces value for org.eclipse.jdt.core.compiler.problem.forbiddenReference to "warning"

Home » Archived » Maven Integration (M2E) » m2e forces value for org.eclipse.jdt.core.compiler.problem.forbiddenReference to "warning"(m2e forces "Deprecated and restricted API" --> "Forbidden reference (access rules)" to WARNING)

m2e forces value for org.eclipse.jdt.core.compiler.problem.forbiddenReference to "warning" [message #715873]

Mon, 15 August 2011 16:18

Eclipse User

Hi all,

Before raise a bug on the bugzilla (there is a open unresolved bug on the old m2e JIRA from sonatype:
https ://issues.sonatype.org/browse/MNGECLIPSE-2170
I want to know if this behavior is for something special or is really a bug.

What this does is change to WARNING the setting under: Project Properties --> Java Compiler --> Errors/Warnings --> Section "Deprecated and restricted API" --> "Forbidden reference (access rules)" no matter if it is set on ERROR or if the default workspace value for this setting is ERROR when you run: Maven --> Update Project Configuration

The JIRA issue points to the old off line SVN. The new GIT location is:
http ://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.jdt/src/org/eclipse/m2e/jdt/internal/AbstractJavaProjectConfigurator.java#n468

Line 468

Thanks
Martin

PS: I put a space before the :// on the links because the forum does not allow me post links because is my first message on the forum (It requires more than 5)

Previous Topic:	Setting POM among Eclipse projects
Next Topic:	Setting POM among Eclipse projects

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 06:52:42 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter