Hi John, Thanks for pointing me at this - apparently I hadn’t submitted my updated GPG key to a key server and it bounced the close. It should be sorted now.
Regards, Tim > On 17 Jun 2016, at 17:36, John Ross <[email protected]> wrote: > > I'm not able to run the verify script against your repository [1]. > > When I go to > https://repository.apache.org/content/repositories/orgapachearies-1072 in > my browser, it says "Repository "orgapachearies-1072 (staging: open)" > [id=orgapachearies-1072] exists but is not exposed." > > I believe this means you need to close the staging repository. > > > [1] > --2016-06-17 11:25:54-- > http://repository.apache.org/content/repositories/orgapachearies-1072/org/apache/aries/ > Resolving repository.apache.org... 140.211.11.112 > Connecting to repository.apache.org|140.211.11.112|:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://repository.apache.org/content/repositories/orgapachearies-1072/org/apache/aries/ > [following] > --2016-06-17 11:25:56-- > https://repository.apache.org/content/repositories/orgapachearies-1072/org/apache/aries/ > Connecting to repository.apache.org|140.211.11.112|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2016-06-17 11:25:56 ERROR 404: Not Found. > > On Thu, Jun 16, 2016 at 6:20 AM, Timothy Ward <[email protected]> > wrote: > >> Hi all, >> >> As I’m sure you’ve seen from list traffic over the last few months I’ve >> been working on an implementation of OSGi RFC 221 in Aries. The project >> provides implementations of both local and XA transactions, as well as >> resource providers for JDBC and JPA. The latter resource provider makes use >> of the Aries JPA container 2.4.0 release. >> >> There has been quite a bit of user interest in the project, and there is >> even an OSGi enRoute example being developed using Aries Transaction >> Control. Because of this It feels to be the right time for a 0.0.1 release. >> This will let people kick the tyres a little harder, and hopefully provide >> a good point for collecting further user feedback. >> >> Obviously the OSGi API being implemented by these components is not final. >> To ensure that this doesn’t case a problem I have done two things. Firstly, >> the projects are being released at a 0.0.x version, secondly, the OSGi API >> packages are being exported with a mandatory attribute of >> api.status=aries.prerelease. This forces users to opt-in to using the API. >> Obviously the attribute will be removed once the OSGi API is finalised. >> >> I’ve staged a repository at >> >> >> https://repository.apache.org/service/local/repositories/orgapachearies-1072 >> >> The main source release is available at >> https://repository.apache.org/service/local/repositories/orgapachearies-1072/content/org/apache/aries/tx-control/tx-control/0.0.1/tx-control-0.0.1-source-release.zip >> >> Please review the artifacts and vote: >> >> [ ] +1 Release the above artifacts >> [ ] -1 Do not >> >> As a PMC member I vote +1 >> >> Best Regards, >> >> Tim >>
