[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] limiting the suggestion list for m2e class auto completion
|
I won't accept this change in m2e core, for two reasons
First, and most importantly, this will be too confusing to explain and
will likely cause additional support traffic.
Second, this can be implemented via m2e extension, so you can implement
this behaviour without polluting m2e core. I can provide some pointers
how to do this on m2e-dev (we try to keep m2e-users for m2e usage
related questions).
--
Regards,
Igor
On 12-11-22 12:55 AM, Titi Wangsa Damhore wrote:
Hi Igor,
I think making it an option that can be ticked on and off would allow
the runtime dependencies to be excluded during development and ticked
back on during running of test cases?
its not an elegant way to do it, but if there is a "hook" of somesort
that can be attached prior to running the test "run as junit test", we
can enable the setting and then disable the setting on test completion?
On Thu, Nov 22, 2012 at 1:48 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:
Removing runtime dependencies from build classpath will break
compilation of test classes at least in some cases.
I don't see a nice way to make this configurable but I am open to ideas.
--
Regards,
Igor
On 12-11-21 11:50 PM, Titi Wangsa Damhore wrote:
I was thinking more along the lines of "compile" and "runtime".
Simply put, "if depdendency is runtime, don't put it in classpath"
or at least have an option to do that
[X] exclude runtime dependency from classpath
On Thu, Nov 22, 2012 at 9:19 AM, Igor Fedorenko
<igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
<mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> wrote:
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
<https://bugs.eclipse.org/bugs/__show_bug.cgi?id=376616>
<https://bugs.eclipse.org/__bugs/show_bug.cgi?id=376616
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=376616>>
[2]
https://bugs.eclipse.org/bugs/____show_bug.cgi?id=224708
<https://bugs.eclipse.org/bugs/__show_bug.cgi?id=224708>
<https://bugs.eclipse.org/__bugs/show_bug.cgi?id=224708
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708>>
[3]
https://bugs.eclipse.org/bugs/____show_bug.cgi?id=356450
<https://bugs.eclipse.org/bugs/__show_bug.cgi?id=356450>
<https://bugs.eclipse.org/__bugs/show_bug.cgi?id=356450
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=356450>>
[4] http://wiki.eclipse.org/M2E_____Development_Environment
<http://wiki.eclipse.org/M2E___Development_Environment>
<http://wiki.eclipse.org/M2E___Development_Environment
<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
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
<mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
https://dev.eclipse.org/____mailman/listinfo/m2e-users
<https://dev.eclipse.org/__mailman/listinfo/m2e-users>
<https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>>
___________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
<mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
https://dev.eclipse.org/____mailman/listinfo/m2e-users
<https://dev.eclipse.org/__mailman/listinfo/m2e-users>
<https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>>
_________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>
_________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users