On Tue, May 16, 2017 at 11:20 AM, < [email protected]> wrote:
> > > Hi Michael, > > thank you for holding off. Fixes for the two issues we wanted resolved are > now on master. > cool Regards, > Arunan > > > > On Wednesday, May 10, 2017 at 10:28:11 AM UTC+1, arunan.bala...@ > interlinksoftware.com wrote: >> >> >> >> Hi Michael, >> >> we are in the middle of porting our stack to Karaf 4.1.1 and would like >> to get two patches upstreamed into pax exam if possible; I've not yet got >> access to the OPS4J Jira to update 815. >> >> https://ops4j1.jira.com/browse/PAXEXAM-723 - my colleague put up a patch >> https://github.com/NetNow/org.ops4j.pax.exam2/commit/5dc57cb >> 012306b5df53b98680b67c34a9b4d47d2?diff=unified that I think got lost in >> the noise. The title of the ticket suggests a breaking change to the >> feature, but the suggested patch has an opt-in option instead. >> https://ops4j1.jira.com/browse/PAXEXAM-815 - there is a branch at >> https://github.com/NetNow/org.ops4j.pax.exam2/tree/configure >> -karaf-logging-by-backend which has allowed me to get logging from the >> console when using log4j2. >> >> These would be handy for us. I also think that more and more people are >> going to hit 815 as they move to Karaf 4.1.x versions, since it uses >> log4j2. I would be happy to action any feedback regarding these two patches >> in order to get them merged and released. >> >> Regards, >> Arunan >> >> >> On Monday, May 8, 2017 at 2:41:02 PM UTC+1, Michael Vorburger wrote: >>> >>> Hello, >>> >>> In order to be able to benefit from https://ops4j1.jira.com/browse >>> /PAXEXAM-740 in a downstream project, I would be interested in a Pax >>> Exam release some time. It's not super urgent, but was hoping for maybe the >>> next week or two.. if this fits with other ongoing issues on >>> https://ops4j1.jira.com/projects/PAXEXAM?selectedItem=com. >>> atlassian.jira.jira-projects-plugin:release-page&status=unreleased - >>> what are your plans? >>> >>> Or can I go ahead and just push a pax exam to central as-is now? Latest >>> published is 4.10.0, so shall we have a 4.10.1 next, as there seem to be >>> only 4 small fixes since the 4.10.0. That would be in line with the current >>> 4.10.1-SNAPSHOT in the pom.xml of master .. or do you instead want us to >>> bump master to 4.11.0-SNAPSHOT now, to be in line with JIRA >>> https://ops4j1.jira.com/browse/PAXEXAM-812 and >>> https://ops4j1.jira.com/browse/PAXEXAM-740? >>> >> back to this point.. I still don't have permission to admin versions and set release dates / close / add new versions in JIRA (Achim?). More importantly, it seems to me that the project's original intention probably is to release with bumps to the middle version number, not the last minor version, as this would allow patches in the future to the previous release version? I've therefore just raised https://github.com/ops4j/org.ops4j.pax.exam2/pull/69 to bump master from 4.10.1-SNAPSHOT to 4.11.0-SNAPSHOT in, with the intention of releasing what is now on master as 4.11.0. FYI I just looked around JIRA, have closed the confusing >>> https://ops4j1.jira.com/browse/PAXEXAM-805, and don't see anything else >>> in progress for (4.10.1 or) 4.11.0. >>> >>> BTW in JIRA there are currently 4 open versions (4.11.0, 4.x, 5.0.0 and >>> unscheduled; but no 4.10.1), so prior to a release perhaps the open 4.x >>> issues should perhaps be moved to no version (unscheduled?), and 4.x >>> closed, to avoid confusion? >>> >> Would someone with more permissions in JIRA than I have like to do this clean up? -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
