[
https://issues.apache.org/jira/browse/MGPG-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823642#comment-17823642
]
ASF GitHub Bot commented on MGPG-110:
-------------------------------------
cstamas opened a new pull request, #78:
URL: https://github.com/apache/maven-gpg-plugin/pull/78
It was validating POMs as "Maven2".
These POMs should be handled as "new projects" and they must have strict
validation in effect instead.
---
https://issues.apache.org/jira/browse/MGPG-110
> The sign-and-deploy-file mojo POM validation is off
> ---------------------------------------------------
>
> Key: MGPG-110
> URL: https://issues.apache.org/jira/browse/MGPG-110
> Project: Maven GPG Plugin
> Issue Type: Improvement
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.2.0
>
>
> It uses Maven 2.0 validation, I guess for historical reasons.
> When someone "sign and deploy" POM, it should be treated as "new project",
> hence it needs "strict" validation instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
