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

Version updates ignore import scoped BOM dependencies #25

Closed
drekbour opened this issue Sep 30, 2015 · 1 comment
Closed

Version updates ignore import scoped BOM dependencies #25

drekbour opened this issue Sep 30, 2015 · 1 comment

Comments

@drekbour
Copy link

Version 2.2

As per http://stackoverflow.com/questions/7609876/how-to-make-maven-versionsuse-latest-versions-step-up-import-scoped-entry-in-de

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>se.company.maven</groupId>
            <artifactId>maven-third-party-dependencies</artifactId>
            <version>0.0.1</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

When we run mvn versions:use-latest-versions all our dependencies (and other entries in dependencyManagement) get stepped up except this one.

tavin added a commit to tavin/versions-maven-plugin that referenced this issue Feb 8, 2016
tavin added a commit to tavin/versions-maven-plugin that referenced this issue Feb 9, 2016
@tavin
Copy link
Contributor

tavin commented May 23, 2016

see pull request above -- we've been using my patch for 3+ months with no problems

@khmarbaise
@hboutemy

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

No branches or pull requests

2 participants