maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MGPG-19) Site descriptor does not get signed
Date Tue, 12 Jan 2010 22:55:55 GMT

    [ http://jira.codehaus.org/browse/MGPG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206718#action_206718
] 

Brett Porter commented on MGPG-19:
----------------------------------

it should be getting into the local repository first, as that's how the deploy mechanism works.
However, that'd be a one off solution - sounds like a Maven issue that the metadata can't
be enumerated. Perhaps it is better to change the site plugin to attach it as an artifact
instead (it probably should be anyway?)

> Site descriptor does not get signed
> -----------------------------------
>
>                 Key: MGPG-19
>                 URL: http://jira.codehaus.org/browse/MGPG-19
>             Project: Maven 2.x GPG Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-4
>            Reporter: Stephen Connolly
>            Priority: Blocker
>
> When the site descriptor is an attached artifact, the GPG signature is not generated.
> Steps to reproduce:
> svn co https://svn.apache.org/repos/asf/maven/surefire/tags/surefire-2.5@898285 surefire-2.5
> cd surefire-2.5
> mvn site:attach-descriptor gpg:sign -Papache-release -N
> ls target/*.asc
> if there is a surefire-2.5-site.xml.asc then this bug is fixed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message