[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] feature request
|
On 11/30/2011 05:27 PM, Igor Fedorenko wrote:
Have you tried Dependency Hierarchy pom.xml editor tab? It provides
sorting, searching and filtering to help understand project dependencies
and where they come from.
For sorting in Package Explorer view, add yourself to [1] JDT
enhancement request. There is nothing we can do in m2e until this is
solved in JDT.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=223318
--
Regards,
Igor
On 11-11-30 4:25 PM, Steve Cohen wrote:
It would be nice if the Maven Dependencies pseudo-folder in the Project
Dependencies allowed itself to be sorted from A-Z. Try hunting through
the list when wanting to explore something in a project depending on the
JBoss runtime, for example. Maddening. Can't it at least be sorted
alphabetically by default if a sort control is not available?
Thanks
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Yes, I've done that, but that isn't relevant to my purpose here, which
is not to understand the dependencies, but rather to use Eclipse's
facility to browse inside one of the dependent jars. You can do that
from the Maven Dependencies pseudo folder in the Project Explorer view,
but you can't do that from dependency hierarchy - nor should you be able
to - that's not the purpose of the dependency hierarchy view.
Why would I want to do that? There are many non-source files in
dependent jars such as, in my jboss example, configuration files and
schemas. Often I know which jar a file is in, but finding that jar can
be an annoyance when the Maven Dependencies list is three screens long
and unsorted. That is the reason for my feature request and I don't
think your suggestion helps with this particular use case.
Steve
