[GitHub] [maven-release] michael-o commented on issue #45: adjust expected test result to account for different operating systems

michael-o commented on issue #45: adjust expected test result to account for different operating systems URL: https://github.com/apache/maven-release/pull/45#issuecomment-612607250 Does this reproduce repeatedley on Jenkins?

[GitHub] [maven-release] michael-o commented on issue #45: adjust expected test result to account for different operating systems

michael-o commented on issue #45: adjust expected test result to account for different operating systems URL: https://github.com/apache/maven-release/pull/45#issuecomment-612604539 I ran the ITs multiple times. I cannot reproduce it. Maybe there are zombie processes locking the files? This

[GitHub] [maven-release] michael-o commented on issue #45: adjust expected test result to account for different operating systems

michael-o commented on issue #45: adjust expected test result to account for different operating systems URL: https://github.com/apache/maven-release/pull/45#issuecomment-612599983 Running tests... This is an automated messag

[GitHub] [maven-release] michael-o commented on issue #45: adjust expected test result to account for different operating systems

michael-o commented on issue #45: adjust expected test result to account for different operating systems URL: https://github.com/apache/maven-release/pull/45#issuecomment-612599894 I consider `org.codehaus.plexus.util.cli.Commandline` conceptionally broken because it uses the local shell t

[GitHub] [maven-release] michael-o commented on issue #45: adjust expected test result to account for different operating systems

michael-o commented on issue #45: adjust expected test result to account for different operating systems URL: https://github.com/apache/maven-release/pull/45#issuecomment-612406802 I will look at this casefllly tonight. Can you also explain why the previous change was necessary? -