You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andrei Arapov (JIRA)" <ji...@apache.org> on 2018/02/13 14:06:00 UTC

[jira] [Comment Edited] (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)

    [ https://issues.apache.org/jira/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362360#comment-16362360 ] 

Andrei Arapov edited comment on MNG-5064 at 2/13/18 2:05 PM:
-------------------------------------------------------------

I confirm, that the same issue happens for me. 
{code:java}
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z)
Maven home: /usr/share/maven
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.9.60-linuxkit-aufs", arch: "amd64", family: "unix"
{code}
 


was (Author: andremoniy):
I confirm, that same issue happens for me. 

 
{code:java}
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z)
Maven home: /usr/share/maven
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.9.60-linuxkit-aufs", arch: "amd64", family: "unix"
{code}
 

> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-5064
>                 URL: https://issues.apache.org/jira/browse/MNG-5064
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.0.3
>            Reporter: Geoffrey De Smet
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 3.0.4
>
>
> Here's the command I ran (on a fresh morning, because our update policy is daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml (2 KB at 1.8 KB/sec)
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom (6 KB at 6.0 KB/sec)
> ...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method signature (and I hadn't pulled the changes to deal with that yet).
> - ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)