Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create UI for viewing dependencies #372

Open
rwinch opened this issue Feb 13, 2017 · 4 comments
Open

Create UI for viewing dependencies #372

rwinch opened this issue Feb 13, 2017 · 4 comments

Comments

@rwinch
Copy link

rwinch commented Feb 13, 2017

It would be very helpful to provide a UI (similar to m2e) for viewing the dependencies and dependency tree within Eclipse. This is a key source of frustration for me when working on large projects and trying to sort out classpath issues.

NOTE: I realize that I can use the CLI, but with large number of dependencies this is difficult to use. For example, trying to follow | up 20 dependencies to its parent dependency is difficult. I can use dependencyInsight, but I don't want to run this command a dozen times to sort out classpath issues.

@oehme
Copy link
Member

oehme commented Feb 13, 2017

This would certainly be a useful feature, but has low priority at the moment, since build scans provide the same functionality.

@rwinch
Copy link
Author

rwinch commented Feb 13, 2017

@oehme Thank you for the response. From my perspective build scans are not ideal

  • Build scans require addtional setup (required email is not very user friendly for such a simple task)
  • Many users are not allowed to publish their builds to the internet. They could use Gradle Enterprise, but they may not be in control of this either.
  • Build Scans don't work for users working without internet

I think this should be a higher priority because not being able to easily inspect dependencies is a big disadvantage to Maven.

@oehme
Copy link
Member

oehme commented Feb 13, 2017

I understand the value of such a view, but it is just not high priority enough for us to build it ourselves at the moment. We are happy to guide contributions of course.

@ZeeD
Copy link

ZeeD commented Jan 27, 2023

Sorry to ping on this old issue, but it's possible to reconsider the priority?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants