Short answer, yes, this was requested before, see bug 376616 [1], but implementation is not possible until bug 224708 [2] and bug 356450 [3] are addressed by jdt development team.
m2e development environment setup is explained in [4] and we accept patches following standard eclipse dev process. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=376616 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708 [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=356450 [4] http://wiki.eclipse.org/M2E_Development_Environment -- Regards, Igor On 12-11-21 2:05 PM, Titi Wangsa Damhore wrote:
Hello all, I sort of a newbie, so please be gentle. Currently m2e integrates very well with eclipse. I have slf4j marked as a compile-scoped dependency and when I type "Logger[Ctrl+space]", slf4j Logger is on the list. However, "com.atomikos.logging.Logger", also shows up on this list. I have marked it as a "runtime" scope. I don't want some class marked a "runtime" dependency to show up for code completion. I want m2e to be smart enough to know what some classes should be filtered out. How can I contribute to the m2e project? I am not sure if this is part of "eclipse core" or "m2e" or if it requires changes from both sides. I am not sure if this is something that other people want too. Sorry for the bad english. Its not my native tounge. Thanks. _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
