[
https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed GERONIMO-5309.
-----------------------------------
Resolution: Won't Fix
Closing old outdated issues.
Note that the Apache Geronimo Application Server itself was declared EOL in
2017 and we do not maintain the server parts anymore.
We still do actively maintain many of the Java EE / Jakarta EE which saw the
light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please
feel free to reopen the ticket.
thanks, your Apache Geronimo team!
> 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 Richard Hogstrom
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
