[jira] [Updated] (MGPG-93) .asc files are written to a non-existent output directory
[
https://issues.apache.org/jira/browse/MGPG-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MGPG-93:
Fix Version/s: (was: 3.2.0)
> .asc files are written to a non-existent output directory
> -
>
> Key: MGPG-93
> URL: https://issues.apache.org/jira/browse/MGPG-93
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Pawel Veselov
>Assignee: Tamas Cservenak
>Priority: Major
> Attachments: gpg-test.tar.gz
>
>
> I think this is an instance of MGPG-44, but for a different assembly.
> Attempting to sign .war files created in non-standard location causes build
> to fail:
> {noformat}
> $ mvn package gpg:sign
> [INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
> gpg: using "856916A457583513" as default secret key for signing
> gpg: can't create
> '/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
> such file or directory
> gpg: signing failed: No such file or directory
> {noformat}
> Structure to reproduce: [^gpg-test.tar.gz]
> This can be worked around with using {{ascDirectory}}, but I figured it
> should work without it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MGPG-93) .asc files are written to a non-existent output directory
[
https://issues.apache.org/jira/browse/MGPG-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MGPG-93:
Fix Version/s: 3.2.0
> .asc files are written to a non-existent output directory
> -
>
> Key: MGPG-93
> URL: https://issues.apache.org/jira/browse/MGPG-93
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Pawel Veselov
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: gpg-test.tar.gz
>
>
> I think this is an instance of MGPG-44, but for a different assembly.
> Attempting to sign .war files created in non-standard location causes build
> to fail:
> {noformat}
> $ mvn package gpg:sign
> [INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
> gpg: using "856916A457583513" as default secret key for signing
> gpg: can't create
> '/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
> such file or directory
> gpg: signing failed: No such file or directory
> {noformat}
> Structure to reproduce: [^gpg-test.tar.gz]
> This can be worked around with using {{ascDirectory}}, but I figured it
> should work without it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MGPG-93) .asc files are written to a non-existent output directory
[
https://issues.apache.org/jira/browse/MGPG-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pawel Veselov updated MGPG-93:
--
Description:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
This can be worked around with using {{ascDirectory}}, but I figured it should
work without it.
was:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
This can be worked around with using {{ascDirectory}}, but I figured it should
work it.
> .asc files are written to a non-existent output directory
> -
>
> Key: MGPG-93
> URL: https://issues.apache.org/jira/browse/MGPG-93
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Pawel Veselov
>Priority: Major
> Attachments: gpg-test.tar.gz
>
>
> I think this is an instance of MGPG-44, but for a different assembly.
> Attempting to sign .war files created in non-standard location causes build
> to fail:
> {noformat}
> $ mvn package gpg:sign
> [INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
> gpg: using "856916A457583513" as default secret key for signing
> gpg: can't create
> '/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
> such file or directory
> gpg: signing failed: No such file or directory
> {noformat}
> Structure to reproduce: [^gpg-test.tar.gz]
> This can be worked around with using {{ascDirectory}}, but I figured it
> should work without it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MGPG-93) .asc files are written to a non-existent output directory
[
https://issues.apache.org/jira/browse/MGPG-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pawel Veselov updated MGPG-93:
--
Description:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
This can be worked around with using {{ascDirectory}}, but I figured it should
work it.
was:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
This can be worked around with using `ascDirectory`, but I figured it should
work it.
> .asc files are written to a non-existent output directory
> -
>
> Key: MGPG-93
> URL: https://issues.apache.org/jira/browse/MGPG-93
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Pawel Veselov
>Priority: Major
> Attachments: gpg-test.tar.gz
>
>
> I think this is an instance of MGPG-44, but for a different assembly.
> Attempting to sign .war files created in non-standard location causes build
> to fail:
> {noformat}
> $ mvn package gpg:sign
> [INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
> gpg: using "856916A457583513" as default secret key for signing
> gpg: can't create
> '/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
> such file or directory
> gpg: signing failed: No such file or directory
> {noformat}
> Structure to reproduce: [^gpg-test.tar.gz]
> This can be worked around with using {{ascDirectory}}, but I figured it
> should work it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MGPG-93) .asc files are written to a non-existent output directory
[
https://issues.apache.org/jira/browse/MGPG-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pawel Veselov updated MGPG-93:
--
Description:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
This can be worked around with using `ascDirectory`, but I figured it should
work it.
was:
I think this is an instance of MGPG-44, but for a different assembly.
Attempting to sign .war files created in non-standard location causes build to
fail:
{noformat}
$ mvn package gpg:sign
[INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
gpg: using "856916A457583513" as default secret key for signing
gpg: can't create
'/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
such file or directory
gpg: signing failed: No such file or directory
{noformat}
Structure to reproduce: [^gpg-test.tar.gz]
> .asc files are written to a non-existent output directory
> -
>
> Key: MGPG-93
> URL: https://issues.apache.org/jira/browse/MGPG-93
> Project: Maven GPG Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Pawel Veselov
>Priority: Major
> Attachments: gpg-test.tar.gz
>
>
> I think this is an instance of MGPG-44, but for a different assembly.
> Attempting to sign .war files created in non-standard location causes build
> to fail:
> {noformat}
> $ mvn package gpg:sign
> [INFO] --- maven-gpg-plugin:3.0.1:sign (default-cli) @ b ---
> gpg: using "856916A457583513" as default secret key for signing
> gpg: can't create
> '/home/vps/tmp/gpg-test/mod/target/gpg/../artifacts/b-1-SNAPSHOT.war.asc': No
> such file or directory
> gpg: signing failed: No such file or directory
> {noformat}
> Structure to reproduce: [^gpg-test.tar.gz]
> This can be worked around with using `ascDirectory`, but I figured it should
> work it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
