Managed JPA requirements at OSGi

Hi all, Just thought I'd make everyone here aware that there is new work being done in OSGi to create a specification around doing managed JPA in OSGi. Given the JPA implementation in Aries there might be some interest in this. The current RFP (=requirements document) is here:

[VOTE] Release Aries Subsystems 2.0.2

Hi, Subsystems 2.0.1 was released yesterday, but it contained a serious bug which made it not usable with the Felix Bundle Repository implementation. Therefore I'm calling a vote on Subsystems 2.0.2, which has this issue resolved. The following modules are part of this release: subsystem-api

[jira] [Resolved] (ARIES-1323) Update blueprint-web ServletContextListener to optionally register NamespaceHandlers

[ https://issues.apache.org/jira/browse/ARIES-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved ARIES-1323. - Resolution: Fixed Update blueprint-web ServletContextListener to optionally register

[jira] [Resolved] (ARIES-1322) Introduce Namespaces annotation

[ https://issues.apache.org/jira/browse/ARIES-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved ARIES-1322. - Resolution: Fixed Introduce Namespaces annotation ---

[jira] [Resolved] (ARIES-1334) NoOsgi SimpleNamespaceHandlerSet should try to resolve relative schema references

[ https://issues.apache.org/jira/browse/ARIES-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved ARIES-1334. - Resolution: Fixed NoOsgi SimpleNamespaceHandlerSet should try to resolve relative schema

[jira] [Created] (ARIES-1340) Upgrade to geronimo transaction manager 3.1.3

Guillaume Nodet created ARIES-1340: -- Summary: Upgrade to geronimo transaction manager 3.1.3 Key: ARIES-1340 URL: https://issues.apache.org/jira/browse/ARIES-1340 Project: Aries Issue Type:

Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1 releases

+1 David On 29 June 2015 at 16:56, Sergey Beryozkin sberyoz...@gmail.com wrote: Hi All This is a vote to support the release of blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web 1.1.1. The staging repository for blueprint-parser-1.3.1 is at

Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1 releases

+1 Christian On 29.06.2015 17:56, Sergey Beryozkin wrote: Hi All This is a vote to support the release of blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web 1.1.1. The staging repository for blueprint-parser-1.3.1 is at

Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1 releases

+1 Dan On 29.06.2015 17:56, Sergey Beryozkin wrote: Hi All This is a vote to support the release of blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web 1.1.1. The staging repository for blueprint-parser-1.3.1 is at

Re: [VOTE] Release Aries Subsystems 2.0.2

+1 Tom From: dav...@apache.org To: dev@aries.apache.org dev@aries.apache.org Date: 06/30/2015 02:24 AM Subject:[VOTE] Release Aries Subsystems 2.0.2 Hi, Subsystems 2.0.1 was released yesterday, but it contained a serious bug which made it not usable with the Felix Bundle

Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1 releases

I was concerned myself, then I checked the Aries release instructions and one option listed was to make sure the (dev) profile gets updated which is what I did. However I only updated dev properties in the released module poms - let me check the whole trunk Sergey On 30/06/15 20:15, Thomas

Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1 releases

Is the intent to leave trunk broken for building while the votes are going on? Right now I can no longer build trunk because it complains about not finding the these soon to be released artifacts. Tom From: David Bosschaert david.bosscha...@gmail.com To: dev@aries.apache.org