[jira] Commented: (MGPG-19) Site descriptor does not get signed

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

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

Dennis Lundberg commented on MGPG-19:
-------------------------------------

I had a look at how the Site Plugin attaches the descriptor. It is attached as metadata to the artifact - not as an attached artifact. ArtifactMetadata has no accessors to any File object, but ProjectArtifactMetadata has a private variable that holds a File. That private variable is used to copy the file to the local repository during install, but again it is private.

Without a file we can't sign it AFAICT. If we install the site descriptor into the local repository *before* we try to sign it, we should be able to access it from the local repo. But I'm not sure how well that works with the life cycle. I think it's a chicken-and-egg problem.

> 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