You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Brian Demers (JIRA)" <ji...@apache.org> on 2010/12/07 21:21:10 UTC

[jira] Commented: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central

    [ https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968938#action_12968938 ] 

Brian Demers commented on GERONIMO-5309:
----------------------------------------

Should be all set now

> Invalid signature for  org.apache.geronimo.genesis:genesis:pom:1.2 at central
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-5309
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5309
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Anders Hammar
>            Assignee: Matt Hogstrom
>         Attachments: genesis-1.2.tar.gz
>
>
> The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven.
> Suggested action:
> 1. Verify the pom at the Apache repo (against the one in svn)
> 2. Resign and deploy to the Apache repo
> 3. It should now be synced to central
> You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.