[jira] [Resolved] (ARIES-953) SPIFly: SPI-Consumer breaks when method has multiple parameters

[ https://issues.apache.org/jira/browse/ARIES-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved ARIES-953. Resolution: Fixed Patch applied in http://svn.apache.org/viewvc?view=revision=1708295 Many

[jira] [Updated] (ARIES-953) SPIFly: SPI-Consumer breaks when method has multiple parameters

[ https://issues.apache.org/jira/browse/ARIES-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated ARIES-953: --- Fix Version/s: spifly-1.0.2 > SPIFly: SPI-Consumer breaks when method has multiple parameters

[jira] [Commented] (ARIES-1166) JMX Whiteboard should also accept interfaces ending in MXBean, not just MBean

[ https://issues.apache.org/jira/browse/ARIES-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954555#comment-14954555 ] Michael Taeschner commented on ARIES-1166: -- Hi Frank, thanks for providing the patch. Looks

Re: October board report

Awesome. Makes things much easier. Thx On 12 Oct 2015 19:36, "Christian Schneider" wrote: > Hi Jeremy, > > Dan just made me aware of the reporter tool: > https://reporter.apache.org/ > > This is what it has for Aries. > > Christian > - > > Report from the Apache

Re: October board report

Looks like the releases section is not accurate... David On 13 October 2015 at 11:57, Jeremy Hughes wrote: > Awesome. Makes things much easier. Thx > On 12 Oct 2015 19:36, "Christian Schneider" wrote: > >> Hi Jeremy, >> >> Dan just made me aware of

Re: October board report

True. Probably indicates we're not putting all our releases in jira. On Tue, 13 Oct 2015 12:02 David Bosschaert wrote: > Looks like the releases section is not accurate... > > David > > On 13 October 2015 at 11:57, Jeremy Hughes wrote: > >

Re: October board report

This is the versions view for Aries in jira: https://issues.apache.org/jira/browse/ARIES/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel For the projects to be released by bundle there should be versions on the bundle level. For the projects to be released by subproject the

Re: October board report

"I did put the JPA and Transaction releases in jira." I'm not quite sure what that means. Does it mean there was a ticket open that tracked the release? Does it mean you added the release version to the system so that it can be referenced by the "Fix Version/s" field? Both? Something else? On

Re: October board report

I suppose we should agree on a format so the information is consistent. Some of the ways I can think of that could be used to enter the subsystems release information include the following. SUBSYSTEM-2.0.4 SUBSYSTEM-OBR-1.0.4 Apache Aries Subsystem 2.0.4 Apache Aries Subsystem OBR 2.0.4

Re: October board report

The versions I used in JIRA were subsystem-2.0.4 and subsystem-obr-1.0.4, so I suppose I should use those on https://reporter.apache.org/addrelease.html?aries, especially if we're hopeful of some future integration. I'm not sure if these represent the preferred format, however. On Tue, Oct 13,

Re: October board report

I don't know exactly what "version management in jira" is referencing. Is there a link? On Tue, Oct 13, 2015 at 7:55 AM, Christian Schneider wrote: > I typically create jira versions for the next release and the following > release of each bundle or subproject. > So

Re: October board report

I'm teachable if I neglected to do anything as part of the subsystems release. On Tue, Oct 13, 2015 at 6:04 AM, Jeremy Hughes wrote: > True. Probably indicates we're not putting all our releases in jira. > > On Tue, 13 Oct 2015 12:02 David Bosschaert

Re: October board report

I typically create jira versions for the next release and the following release of each bundle or subproject. So people can set fix version to the upcoming release or to the next release to indicate it will not make it for the upcoming release. Then before the voting I make sure all issues of

[jira] [Created] (ARIES-1431) Ability to be able to specify exception types to rollback on and not rollback on

Tim created ARIES-1431: -- Summary: Ability to be able to specify exception types to rollback on and not rollback on Key: ARIES-1431 URL: https://issues.apache.org/jira/browse/ARIES-1431 Project: Aries

Enhance Aries JPA to be able to specify exception types to rollback on and not rollback on

I have been looking at modifying the Aries JPA code to add the Ability to be able to specify exception types to rollback on and not rollback on The current org.apache.aries.jpa.template.JpaTemplate has the following public interface JpaTemplate { R txExpr(TransactionType type, EmFunction