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

Bill commented on MNG-7126:
---------------------------

Okay. Thanks. I'll pass that info along to the rest of our team regarding the 
hijacking of central issue.

As for the debugging, that output was from the Jenkins build process. I'm happy 
to try and facilitate resolution of this issue. I did come up with a ham-fisted 
solution for our issue by priming the repo with the git fetch of the second 
project and execution of the maven "go offline goal" prior to building the 
first project. Then the second build step is done in offline mode. Seems to 
work, but not an idea solution.

> Maven option -nsu --no-snapshot-updates not working
> ---------------------------------------------------
>
>                 Key: MNG-7126
>                 URL: https://issues.apache.org/jira/browse/MNG-7126
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.5.0
>         Environment: Windows/Linux. Doesn't seem to matter.
>            Reporter: Bill
>            Priority: Major
>         Attachments: compass-next-X-output.txt.tar.gz
>
>
> Essentially the option seems to just not work.
> I found that the same issue outlines in the this Jira for Maven 3.0.3 still 
> applies to Maven 3.5.0: https://issues.apache.org/jira/browse/MNG-5064
> https://issues.apache.org/jira/browse/MNG-5064
> Here someone is mentioning still having the issue Maven 3.2.5: 
> [https://issues.maven.apache.narkive.com/gF3CQyTF/jira-commented-mng-5064-mvn-nsu-no-snapshot-updates-should-not-download-snapshots-and-break-local]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to