[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584991#comment-16584991 ] ASF GitHub Bot commented on MPLUGIN-336: sormuras commented on issue #14: [MPLUGIN-336] Upgrade

[GitHub] sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414100898 Thanks for the prompt and detailed reply. This is an

[jira] [Commented] (SCM-797) gitexe checkIn() fails due to Windows command line length limitation

[ https://issues.apache.org/jira/browse/SCM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584972#comment-16584972 ] ASF GitHub Bot commented on SCM-797: gmcdonald closed pull request #49: SCM-797: Workaround for Windows

[GitHub] gmcdonald closed pull request #22: Implementation for Secure FTP (FTPS protocol)

gmcdonald closed pull request #22: Implementation for Secure FTP (FTPS protocol) URL: https://github.com/apache/maven-wagon/pull/22 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] gmcdonald closed pull request #49: SCM-797: Workaround for Windows command line length limitation

gmcdonald closed pull request #49: SCM-797: Workaround for Windows command line length limitation URL: https://github.com/apache/maven-scm/pull/49 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance:

[jira] [Updated] (SCM-860) add goal creates creates wrong paths if parent pom is not at root directory

[ https://issues.apache.org/jira/browse/SCM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-860: --- Fix Version/s: waiting-for-feedback > add goal creates creates wrong paths if parent pom is not at root

[jira] [Commented] (SCM-860) add goal creates creates wrong paths if parent pom is not at root directory

[ https://issues.apache.org/jira/browse/SCM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584960#comment-16584960 ] Michael Osipov commented on SCM-860: It is the GitExe Provider. Can you try with JGit? Can you provide a

[jira] [Commented] (SCM-643) release:branch in mercurial provider updates the version in the new branch

[ https://issues.apache.org/jira/browse/SCM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584958#comment-16584958 ] Michael Osipov commented on SCM-643: Is this still valid? If yes, can someone update the patch? >

[jira] [Updated] (SCM-643) release:branch in mercurial provider updates the version in the new branch

[ https://issues.apache.org/jira/browse/SCM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-643: --- Fix Version/s: waiting-for-feedback > release:branch in mercurial provider updates the version in the

[jira] [Updated] (SCM-651) HgChangeLogCommand ignores ScmBranch

[ https://issues.apache.org/jira/browse/SCM-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-651: --- Fix Version/s: (was: 1.x) waiting-for-feedback > HgChangeLogCommand ignores

[jira] [Commented] (SCM-651) HgChangeLogCommand ignores ScmBranch

[ https://issues.apache.org/jira/browse/SCM-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584957#comment-16584957 ] Michael Osipov commented on SCM-651: Though, it has been years: can we can an updated patch and I will

[jira] [Updated] (SCM-665) TfsChangeLogCommand does not display the change log for directories

[ https://issues.apache.org/jira/browse/SCM-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-665: --- Fix Version/s: waiting-for-feedback > TfsChangeLogCommand does not display the change log for

[jira] [Commented] (SCM-665) TfsChangeLogCommand does not display the change log for directories

[ https://issues.apache.org/jira/browse/SCM-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584956#comment-16584956 ] Michael Osipov commented on SCM-665: Is this still valid? According to the docs, it can be a directory.

[jira] [Updated] (SCM-843) New files added to index are not checked in when nothing else has been changed in the working copy

[ https://issues.apache.org/jira/browse/SCM-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-843: --- Fix Version/s: waiting-for-feedback > New files added to index are not checked in when nothing else has

[jira] [Commented] (SCM-843) New files added to index are not checked in when nothing else has been changed in the working copy

[ https://issues.apache.org/jira/browse/SCM-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584954#comment-16584954 ] Michael Osipov commented on SCM-843: I'd be happy to commit this if I get a PR and a unit test for that.

[jira] [Updated] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-777: --- Fix Version/s: waiting-for-feedback > Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl

[jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584953#comment-16584953 ] Michael Osipov commented on SCM-777: I think this works now spite the comment because the boolean value

[jira] [Updated] (SCM-851) "isCheckinPoliciesEnabled" is treated as mandatory in TFS URL

[ https://issues.apache.org/jira/browse/SCM-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-851: --- Fix Version/s: waiting-for-feedback > "isCheckinPoliciesEnabled" is treated as mandatory in TFS URL >

[jira] [Commented] (SCM-851) "isCheckinPoliciesEnabled" is treated as mandatory in TFS URL

[ https://issues.apache.org/jira/browse/SCM-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584952#comment-16584952 ] Michael Osipov commented on SCM-851: [~BigJ], still willing to provide the tests? >

[jira] [Closed] (SCM-628) scm:checkout parsing URL for clone does not match what is passed in with -DconnectionUrl

[ https://issues.apache.org/jira/browse/SCM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-628. -- Resolution: Fixed Fixed with

[jira] [Updated] (SCM-628) scm:checkout parsing URL for clone does not match what is passed in with -DconnectionUrl

[ https://issues.apache.org/jira/browse/SCM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-628: --- Fix Version/s: (was: waiting-for-feedback) 1.10.1 > scm:checkout parsing URL for

[jira] [Assigned] (SCM-628) scm:checkout parsing URL for clone does not match what is passed in with -DconnectionUrl

[ https://issues.apache.org/jira/browse/SCM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-628: -- Assignee: Michael Osipov > scm:checkout parsing URL for clone does not match what is passed in

[jira] [Closed] (SCM-745) Perforce blame result parsing too greedy

[ https://issues.apache.org/jira/browse/SCM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-745. -- Resolution: Fixed Fixed with

[jira] [Updated] (SCM-745) Perforce blame result parsing too greedy

[ https://issues.apache.org/jira/browse/SCM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-745: --- Summary: Perforce blame result parsing too greedy (was: Perforce Blame Result Parsing Error) >

[jira] [Assigned] (SCM-745) Perforce Blame Result Parsing Error

[ https://issues.apache.org/jira/browse/SCM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-745: -- Assignee: Michael Osipov > Perforce Blame Result Parsing Error >

[jira] [Updated] (SCM-745) Perforce Blame Result Parsing Error

[ https://issues.apache.org/jira/browse/SCM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-745: --- Fix Version/s: 1.10.1 > Perforce Blame Result Parsing Error > --- > >

[jira] [Commented] (MSITE-827) Site builds rely on HTTP 404

[ https://issues.apache.org/jira/browse/MSITE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584942#comment-16584942 ] Michael Osipov commented on MSITE-827: -- The two {{site.xml}} files is a long standing bug still

[jira] [Commented] (SCM-834) Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584939#comment-16584939 ] Michael Osipov commented on SCM-834: Just pushed a test branch which does for me. Please test. I want to

[jira] [Resolved] (SCM-834) Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov resolved SCM-834. Resolution: Fixed > Commit encoding is platform-dependent instead of UTF-8 >

[GitHub] dfa1 opened a new pull request #22: Cleanups

dfa1 opened a new pull request #22: Cleanups URL: https://github.com/apache/maven-release/pull/22 Minor code cleanups: - adding generics - removing unused test methods This is an automated message from the Apache Git

[jira] [Closed] (SCM-896) Subversion config file path incorrectly calculated on Windows

[ https://issues.apache.org/jira/browse/SCM-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-896. -- Resolution: Fixed Fixed with

[jira] [Updated] (SCM-896) Subversion config file path incorrectly calculated on Windows

[ https://issues.apache.org/jira/browse/SCM-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-896: --- Description: The current code {{new File( System.getProperty( "user.home" ), "Application

[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584936#comment-16584936 ] ASF GitHub Bot commented on MPLUGIN-336: forax commented on issue #14: [MPLUGIN-336] Upgrade ASM

[GitHub] forax commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

forax commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414087721 ASM 6.2.1 (and ASM 6.2) are nestmate ready, but you have to opt-in using the api ASM7_EXPERIMENTAL instead of the api ASM6

[jira] [Created] (SCM-896) Subversion config file path incorrectly calculated on Windows

Michael Osipov created SCM-896: -- Summary: Subversion config file path incorrectly calculated on Windows Key: SCM-896 URL: https://issues.apache.org/jira/browse/SCM-896 Project: Maven SCM Issue

[jira] [Commented] (MPLUGIN-339) maven-plugin-tools-javadoc broken by com.sun.tools.doclets removal in Java 10

[ https://issues.apache.org/jira/browse/MPLUGIN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584931#comment-16584931 ] Karl Heinz Marbaise commented on MPLUGIN-339: - For JDK 10 you have to use

[jira] [Created] (MPLUGIN-342) Upgrade maven-parent to 32.

Karl Heinz Marbaise created MPLUGIN-342: --- Summary: Upgrade maven-parent to 32. Key: MPLUGIN-342 URL: https://issues.apache.org/jira/browse/MPLUGIN-342 Project: Maven Plugin Tools Issue

[jira] [Updated] (SCM-834) Git Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-834: --- Component/s: maven-scm-provider-svn > Git Commit encoding is platform-dependent instead of UTF-8 >

[jira] [Updated] (SCM-834) Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-834: --- Summary: Commit encoding is platform-dependent instead of UTF-8 (was: Git Commit encoding is

[jira] [Updated] (SCM-834) Git Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-834: --- Priority: Blocker (was: Major) > Git Commit encoding is platform-dependent instead of UTF-8 >

[jira] [Commented] (SCM-834) Git Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584930#comment-16584930 ] Michael Osipov commented on SCM-834: Just made a simple test in Eclipse. It is even worse that that. It

[jira] [Updated] (SCM-834) Git Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-834: --- Fix Version/s: (was: waiting-for-feedback) 1.10.1 > Git Commit encoding is

[jira] [Assigned] (SCM-834) Git Commit encoding is platform-dependent instead of UTF-8

[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-834: -- Assignee: Michael Osipov > Git Commit encoding is platform-dependent instead of UTF-8 >

[jira] [Created] (MSITE-827) Site builds rely on HTTP 404

Stephen Colebourne created MSITE-827: Summary: Site builds rely on HTTP 404 Key: MSITE-827 URL: https://issues.apache.org/jira/browse/MSITE-827 Project: Maven Site Plugin Issue Type: Bug

[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584921#comment-16584921 ] ASF GitHub Bot commented on MPLUGIN-336: sormuras commented on issue #14: [MPLUGIN-336] Upgrade

[GitHub] sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414085266 > ... until ASM API for nests stabilises. @forax Is ASM 6.2.1 ready for nest support? Or will there be another

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584914#comment-16584914 ] ASF GitHub Bot commented on SCM-835: michael-o commented on issue #51: fix SCM-835 collision URL:

[GitHub] michael-o commented on issue #51: fix SCM-835 collision

michael-o commented on issue #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#issuecomment-414084580 I am looking to your PR. Can you please rebase against master? So, if I understood the issue properly, The status consumer also returned unaffected files

[jira] [Updated] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-835: --- Affects Version/s: 1.10.0 > includes directive doesn't work correctly when other files in directory >

[jira] [Updated] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-835: --- Component/s: maven-scm-provider-gitexe > includes directive doesn't work correctly when other files in

[jira] [Commented] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584911#comment-16584911 ] Michael Osipov commented on WAGON-521: -- Well, the issue was closed with the wrapper too. I have

[jira] [Commented] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584906#comment-16584906 ] Noel Grandin commented on WAGON-521: So maven operates on the principle that unless a patch is

[GitHub] michael-o commented on issue #75: add fileNamesOnly property to only show file names

michael-o commented on issue #75: add fileNamesOnly property to only show file names URL: https://github.com/apache/maven-scm/pull/75#issuecomment-414082733 Please create a JIRA ticket first. The change is incomplete since the stdout case produces warnings: > [INFO] Executing:

[jira] [Commented] (SCM-791) GitExe Provider does not work properly in Cygwin

[ https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584902#comment-16584902 ] ASF GitHub Bot commented on SCM-791: asfgit closed pull request #77: SCM-791,SCM-815: fixes for Windows

[jira] [Closed] (SCM-892) URLs aren't set where URLs are expected

[ https://issues.apache.org/jira/browse/SCM-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-892. -- Resolution: Fixed Fixed with

[jira] [Updated] (SCM-815) GitExe Provider does not commit files in Cygwin

[ https://issues.apache.org/jira/browse/SCM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-815: --- Fix Version/s: (was: waiting-for-feedback) 1.10.1 > GitExe Provider does not

[jira] [Closed] (SCM-815) GitExe Provider does not commit files in Cygwin

[ https://issues.apache.org/jira/browse/SCM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-815. -- Resolution: Fixed Assignee: Michael Osipov Fixed with

[jira] [Closed] (SCM-791) GitExe Provider does not work properly in Cygwin

[ https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-791. -- Resolution: Fixed Fixed with

[GitHub] asfgit closed pull request #77: SCM-791, SCM-815: fixes for Windows paths in git command line

asfgit closed pull request #77: SCM-791,SCM-815: fixes for Windows paths in git command line URL: https://github.com/apache/maven-scm/pull/77 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As

[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584899#comment-16584899 ] ASF GitHub Bot commented on MPLUGIN-336: sormuras edited a comment on issue #14: [MPLUGIN-336]

[GitHub] sormuras edited a comment on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

sormuras edited a comment on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414081410 ASM 6.2.1 was released: https://asm.ow2.io/versions.html Tried to compile a plugin with JDK 11 and

[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584896#comment-16584896 ] ASF GitHub Bot commented on MPLUGIN-336: sormuras edited a comment on issue #14: [MPLUGIN-336]

[jira] [Commented] (MPLUGIN-336) broken in JDK 10 - IllegalArgumentException

[ https://issues.apache.org/jira/browse/MPLUGIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584895#comment-16584895 ] ASF GitHub Bot commented on MPLUGIN-336: sormuras commented on issue #14: [MPLUGIN-336] Upgrade

[GitHub] sormuras edited a comment on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

sormuras edited a comment on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414081410 ASM 6.2.1 was released: https://asm.ow2.io/versions.html Tried to compile a plugin with JDK 11 and

[GitHub] sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10, 11 support

sormuras commented on issue #14: [MPLUGIN-336] Upgrade ASM to 6.2 for Java 10,11 support URL: https://github.com/apache/maven-plugin-tools/pull/14#issuecomment-414081410 ASM 6.2.1 was released. Tried to compile a plugin with JDK 11 and `--release 11` yielded: ```text ...

[jira] [Commented] (WAGON-446) SSH agent authentication is no longer working in wagon-ssh 2.10

[ https://issues.apache.org/jira/browse/WAGON-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584893#comment-16584893 ] Michael Osipov commented on WAGON-446: -- Is this one still valid? > SSH agent authentication is no

[jira] [Updated] (WAGON-446) SSH agent authentication is no longer working in wagon-ssh 2.10

[ https://issues.apache.org/jira/browse/WAGON-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-446: - Fix Version/s: waiting-for-feedback > SSH agent authentication is no longer working in wagon-ssh

[jira] [Closed] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-521. Resolution: Won't Fix No investigation nor a patch have been provided. > Maven cannot use system

[jira] [Closed] (WAGON-523) Maven to retry when a download fails

[ https://issues.apache.org/jira/browse/WAGON-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-523. Resolution: Won't Fix Fix Version/s: (was: waiting-for-feedback) No reaction for months.

[jira] [Closed] (WAGON-309) NTLM for webdav behind IIS

[ https://issues.apache.org/jira/browse/WAGON-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-309. Resolution: Won't Fix Fix Version/s: (was: waiting-for-feedback) NTLM is a dead-end. Not

[jira] [Closed] (WAGON-502) Succesfull PUT times out on Nexus

[ https://issues.apache.org/jira/browse/WAGON-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-502. Resolution: Incomplete Fix Version/s: (was: waiting-for-feedback) No information

[jira] [Closed] (WAGON-391) Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false

[ https://issues.apache.org/jira/browse/WAGON-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-391. Resolution: Incomplete Fix Version/s: (was: waiting-for-feedback) No reaction for

[jira] [Updated] (WAGON-491) Being able to set certificate via byte[] not only a file

[ https://issues.apache.org/jira/browse/WAGON-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-491: - Issue Type: New Feature (was: Bug) > Being able to set certificate via byte[] not only a file >

[jira] [Closed] (WAGON-487) Saved password with french accent breaks deployment

[ https://issues.apache.org/jira/browse/WAGON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-487. Resolution: Cannot Reproduce Fix Version/s: (was: waiting-for-feedback) No proper

[jira] [Closed] (WAGON-324) Site cannot be deployed when part of release plugin, scp method used and server uses ECDSA

[ https://issues.apache.org/jira/browse/WAGON-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-324. Resolution: Incomplete Fix Version/s: (was: waiting-for-feedback) No reaction for

[jira] [Commented] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584881#comment-16584881 ] ASF GitHub Bot commented on WAGON-500: -- michael-o commented on issue #44: [WAGON-500] re-enable

[GitHub] michael-o commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest

michael-o commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest URL: https://github.com/apache/maven-wagon/pull/44#issuecomment-414080627 My tests fail locally because it tells me that `cvs` is not available. What now?

[jira] [Updated] (WAGON-500) ScmCvsExeWagonTest should be re-enabled

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-500: - Fix Version/s: 3.1.1 > ScmCvsExeWagonTest should be re-enabled >

[jira] [Updated] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-500: - Summary: Re-enable ScmCvsExeWagonTest (was: ScmCvsExeWagonTest should be re-enabled) >

[GitHub] asfgit closed pull request #28: Add support for detecting and using of KiTTY's klink.exe and kscp.exe

asfgit closed pull request #28: Add support for detecting and using of KiTTY's klink.exe and kscp.exe URL: https://github.com/apache/maven-wagon/pull/28 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[jira] [Closed] (WAGON-525) Support for detecting and using of KiTTY's klink.exe and kscp.exe

[ https://issues.apache.org/jira/browse/WAGON-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-525. Resolution: Fixed Fixed with

[jira] [Comment Edited] (WAGON-525) Support for detecting and using of KiTTY's klink.exe and kscp.exe

[ https://issues.apache.org/jira/browse/WAGON-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584875#comment-16584875 ] Michael Osipov edited comment on WAGON-525 at 8/18/18 7:06 PM: --- Fixed with

[jira] [Updated] (WAGON-525) Support for detecting and using of KiTTY's klink.exe and kscp.exe

[ https://issues.apache.org/jira/browse/WAGON-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-525: - Fix Version/s: 3.1.1 > Support for detecting and using of KiTTY's klink.exe and kscp.exe >

[jira] [Assigned] (WAGON-525) Support for detecting and using of KiTTY's klink.exe and kscp.exe

[ https://issues.apache.org/jira/browse/WAGON-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned WAGON-525: Assignee: Michael Osipov > Support for detecting and using of KiTTY's klink.exe and

[jira] [Comment Edited] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

[ https://issues.apache.org/jira/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584858#comment-16584858 ] Stephen Colebourne edited comment on MSITE-639 at 8/18/18 6:22 PM: --- I

[jira] [Comment Edited] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

[ https://issues.apache.org/jira/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584860#comment-16584860 ] Karl Heinz Marbaise edited comment on MSITE-639 at 8/18/18 6:08 PM:

[jira] [Comment Edited] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

[ https://issues.apache.org/jira/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584860#comment-16584860 ] Karl Heinz Marbaise edited comment on MSITE-639 at 8/18/18 6:06 PM:

[jira] [Commented] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

[ https://issues.apache.org/jira/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584860#comment-16584860 ] Karl Heinz Marbaise commented on MSITE-639: --- Commenting on closed issue is not a good idea

[jira] [Commented] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured

[ https://issues.apache.org/jira/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584858#comment-16584858 ] Stephen Colebourne commented on MSITE-639: -- I can't reopen this (as I don't have permission), but

[jira] [Commented] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584856#comment-16584856 ] Hudson commented on MPOM-205: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #38 See

[jira] [Updated] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-205: --- Description: currently, during Apache release, checksums are not created in target/ directory:

[jira] [Updated] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-205: --- Description: currently, during Apache release, checksums are not created in target/ directory:

[jira] [Updated] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-205: --- Description: currently, during Apache release, checksums are not created in target/ directory:

[jira] [Updated] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-205: --- Summary: create SHA-512 checksum for source-release archive(s) in target/checkout/target/ during

[jira] [Updated] (MPOM-168) JDK 9 requires updates to plugins

[ https://issues.apache.org/jira/browse/MPOM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-168: --- Fix Version/s: (was: ASF-21) ASF-22 > JDK 9 requires updates to plugins >

[jira] [Updated] (MPOM-134) Add profile to use a different resource bundle for incubator projects

[ https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-134: --- Fix Version/s: (was: ASF-21) ASF-22 > Add profile to use a different resource

[jira] [Updated] (MPOM-205) create SHA-512 checksum for source-release archive(s) in target/ during release

[ https://issues.apache.org/jira/browse/MPOM-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-205: --- Description: currently, during Apache release, checksums are not created in target/ directory:

[jira] [Commented] (MJAVADOC-535) Upgrade to parent pom 32

[ https://issues.apache.org/jira/browse/MJAVADOC-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584848#comment-16584848 ] Hudson commented on MJAVADOC-535: - Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin »

[jira] [Closed] (MJAVADOC-535) Upgrade to parent pom 32

[ https://issues.apache.org/jira/browse/MJAVADOC-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MJAVADOC-535. --- Resolution: Fixed > Upgrade to parent pom 32 > > >

[jira] [Commented] (MJAVADOC-535) Upgrade to parent pom 32

[ https://issues.apache.org/jira/browse/MJAVADOC-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584842#comment-16584842 ] Guillaume Boué commented on MJAVADOC-535: - Fixed in

  1   2   >