Does this mean one should rather rely on Eclipse API for markers?

> On 20 Oct 2016, at 15:01, Matthew Piggott <mpigg...@sonatype.com> wrote:
> 
> The comment seems to suggest it could be refactored - 
> https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/markers/IMavenMarkerManager.java#L27
>  
> <https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/markers/IMavenMarkerManager.java#L27>
> 
> 
> 
> On 20 October 2016 at 05:20, Konrad Windszus <konra...@gmx.de 
> <mailto:konra...@gmx.de>> wrote:
> 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
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users 
> <https://dev.eclipse.org/mailman/listinfo/m2e-users>
> 
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to