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

use-dep-version (and other goals) does not handle the import-scoped dependency #395

Closed
JohnWu-Pro opened this issue May 11, 2020 · 4 comments

Comments

@JohnWu-Pro
Copy link

@janhicken
Copy link

This seems to be a duplicate of #346.
The PomHelper already features a method to find the imported POMs inside the dependency management section. This is just not used in many of this plugin's goals. The commit referenced in #346 shows a possible fix for the goal use-latest-releases.

@cemo
Copy link

cemo commented May 14, 2020

Same for versions:compare-dependencies. I would like to compare my dependencies which is imported into the project with the remote pom.

@frode-carlsen
Copy link

frode-carlsen commented Aug 2, 2021

I've createad a PR that also will update the import scoped dependencies for the following goals:

  • use-dep-version
  • use-latest-versions
  • use-latest-snapshots
  • use-latest-release
  • use-next-releases
  • use-next-versions
  • use-next-snapshots

#476

agaengel pushed a commit to agaengel/versions-maven-plugin that referenced this issue Sep 3, 2021
@github-actions
Copy link

github-actions bot commented Sep 4, 2022

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.

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