maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Fredén (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
Date Thu, 11 Aug 2016 11:43:20 GMT

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

Christopher Fredén commented on MNG-5064:
-----------------------------------------

I would also want to see this issue reopened. I'm currently using Maven 3.3.9 and the {{\-nsu/--no-snapshot-updates}}
have no effect. This is extremely frustrating and makes it very hard to use maven when building
multiple local projects that depend on each other. I don't have this problem when using Maven
3.0.5 though.

{code}
mvn -v 
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: /nix/store/idqkpb1dx3544nlp9y948bvbipnd2gzs-apache-maven-3.3.9/maven 
Java version: 1.8.0_102, vendor: Oracle Corporation 
Java home: /nix/store/2wpybw1df139dc366ra8qc3i2g3whfd5-openjdk-8u102b04/lib/openjdk/jre 
Default locale: en_US, platform encoding: UTF-8 
OS name: "linux", version: "4.4.13-1-manjaro", 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
(v6.3.4#6332)

Mime
View raw message