You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org> on 2011/04/13 09:35:22 UTC
[jira] Created: (MNG-5064) mvn -nsu (--no-snapshot-updates) should
not download snapshots (and break local builds)
mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
---------------------------------------------------------------------------------------
Key: MNG-5064
URL: http://jira.codehaus.org/browse/MNG-5064
Project: Maven 2 & 3
Issue Type: Bug
Components: Command Line
Affects Versions: 3.0.3
Reporter: Geoffrey De Smet
Priority: Critical
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5064) mvn -nsu (--no-snapshot-updates) should
not download snapshots (and break local builds)
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-5064.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann (was: Benson Margulies)
Fixed in [r1151418|http://svn.apache.org/viewvc?view=revision&revision=1151418].
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-5064) mvn -nsu
(--no-snapshot-updates) should not download snapshots (and break local
builds)
Posted by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336 ]
Geoffrey De Smet edited comment on MNG-5064 at 7/27/11 3:13 AM:
----------------------------------------------------------------
Note, we do have this is in our parent pom:
{code}
<repositories>
<repository>
<id>jboss-public-repository-group</id>
...
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
{code}
But the -nsu should take precedence over that updatePolicy=daily, because command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot (as previous snapshots might be binary incompatible)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify your local changes and you don't want the latest snapshot (which might be binary incompatible)
was (Author: ge0ffrey):
Note, we do have this is in our parent pom:
{code}
<repositories>
<repository>
<id>jboss-public-repository-group</id>
...
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
{code}
But the -nsu should take precedence over that updatePolicy=daily
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates)
should not download snapshots (and break local builds)
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271653#comment-271653 ]
Benson Margulies commented on MNG-5064:
---------------------------------------
/Users/benson/asf/mvn/core-integration-testing/core-it-suite svn log -r1140365
------------------------------------------------------------------------
r1140365 | bimargulies | 2011-06-27 19:17:28 -0400 (Mon, 27 Jun 2011) | 2 lines
[MNG-5064]: add a test that seems to prove that this problem does not, in fact, exist.
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates)
should not download snapshots (and break local builds)
Posted by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274335#comment-274335 ]
Geoffrey De Smet commented on MNG-5064:
---------------------------------------
Yet I have replicated it a couple of days on the command line. Strange.
Maybe, there's a difference between the command line and the test environment?
I am using maven 3.0.3.
Here's a replication of what I did (although there's might be a shorter reproduce recipe):
{code}
// Use maven 3.0.3 on linux
$ git clone git@github.com:droolsjbpm/droolsjbpm-build-bootstrap.git
// clones droolsjbpm-knowledge, then drools, then drools-planner, ...
$ droolsjbpm-build-bootstrap/script/git-clone-others.sh
// builds droolsjbpm-knowledge, then drools, then drools-planner, ...
$ droolsjbpm-build-bootstrap/script/mvn-all.sh clean install -DskipTests
// Note: drools-planner depends on a SNAPSHOT of drools
// Wait one day
$ cd drools-planner
$ mvn clean install -nsu -DskipTests
// It downloads drools-20110727-... pom and jar
{code}
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates)
should not download snapshots (and break local builds)
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271652#comment-271652 ]
Benson Margulies commented on MNG-5064:
---------------------------------------
I just added an integration test to maven that does the right thing (doesn't download snapshots). It passes.
Perhaps you could offer some additional thought as to what might be going on here?
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-5064) mvn -nsu
(--no-snapshot-updates) should not download snapshots (and break local
builds)
Posted by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336 ]
Geoffrey De Smet edited comment on MNG-5064 at 7/27/11 3:13 AM:
----------------------------------------------------------------
Note, we do have this is in our parent pom:
{code}
<repositories>
<repository>
<id>jboss-public-repository-group</id>
...
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
{code}
But the -nsu should take precedence over that updatePolicy=daily, because command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot (as previous snapshots might be binary incompatible with the latest code)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify your local changes and you don't want the latest snapshot (which might be binary incompatible because you don't have the latest code)
was (Author: ge0ffrey):
Note, we do have this is in our parent pom:
{code}
<repositories>
<repository>
<id>jboss-public-repository-group</id>
...
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
{code}
But the -nsu should take precedence over that updatePolicy=daily, because command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot (as previous snapshots might be binary incompatible)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify your local changes and you don't want the latest snapshot (which might be binary incompatible)
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates)
should not download snapshots (and break local builds)
Posted by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336 ]
Geoffrey De Smet commented on MNG-5064:
---------------------------------------
Note, we do have this is in our parent pom:
{code}
<repositories>
<repository>
<id>jboss-public-repository-group</id>
...
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
{code}
But the -nsu should take precedence over that updatePolicy=daily
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
> ---------------------------------------------------------------------------------------
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0.3
> Reporter: Geoffrey De Smet
> Assignee: Benson Margulies
> Priority: Critical
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira