[m2e-users] API class AbstractProjectConfigurator exposes access to inte

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[m2e-users] API class AbstractProjectConfigurator exposes access to internal IMarkerManager

From: Konrad Windszus <konrad_w@xxxxxx>
Date: Thu, 20 Oct 2016 11:20:12 +0200
Delivered-to: m2e-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-users>
List-help: <mailto:m2e-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=unsubscribe>

Whenever I access the markerManager in my custom project configurator derived from org.eclipse.m2e.core.project.configurator.AbstractProjectConfigurator I get a "Discouraged Access" warning, because the class IMavenMarkerManager is located in an internal package "org.eclipse.m2e.core.internal.markers". Is that deliberate? What is the recommended way to add markers in my custom project configurator? Using plain Eclipse API only? Or is it safe to assume that the IMavenMarkerManager is pretty stable?
Thanks,
Konrad

Follow-Ups:
- Re: [m2e-users] API class AbstractProjectConfigurator exposes access to internal IMarkerManager
  - From: Matthew Piggott

Prev by Date: Re: [m2e-users] https://repository.takari.io certificate expires
Next by Date: Re: [m2e-users] API class AbstractProjectConfigurator exposes access to internal IMarkerManager
Previous by thread: [m2e-users] https://repository.takari.io certificate expires
Next by thread: Re: [m2e-users] API class AbstractProjectConfigurator exposes access to internal IMarkerManager
Index(es):
- Date
- Thread

Breadcrumbs