You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2020/01/19 21:49:00 UTC
[jira] [Updated] (MSHARED-851) & must trigger quoting in Windows
[ https://issues.apache.org/jira/browse/MSHARED-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz updated MSHARED-851:
-----------------------------------------
Description:
When trying to use the latest maven-jarsign-plugin using a keystore-password which contains with character &, signing failed.
Create quoting functionality, similar to one for Bash script BourneShell.java should fix the problem.
was:
When trying to use the latest maven-jarsign-plugin using a keystore-password which started with a hash (#), signing failed. After enabling debug output with -X, I got a strange debug message:
[DEBUG] Option lacks argument
Since signtool is invoked using /bin/sh -c ..., of course, any # must be quoted, because otherwise it acts as a comment-start and thus effectively cuts-off the rest of the cmdline.
After single-quoting the password in the pom.xml, the jar signing was ok.
=>
Adding '#' to BASH_QUOTING_TRIGGER_CHARS in org.apache.maven.shared.utils.cli.shell.BourneShell.java should fix the problem.
Environment: Windows (was: Unix (Linux))
> & must trigger quoting in Windows
> ---------------------------------
>
> Key: MSHARED-851
> URL: https://issues.apache.org/jira/browse/MSHARED-851
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-shared-utils
> Environment: Windows
> Reporter: Sylwester Lachiewicz
> Priority: Major
>
> When trying to use the latest maven-jarsign-plugin using a keystore-password which contains with character &, signing failed.
> Create quoting functionality, similar to one for Bash script BourneShell.java should fix the problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)