You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Andreas Pieber <an...@gmail.com> on 2012/02/17 06:55:51 UTC
Preparing Pax Exam 2.3.1 release
Hey Guys,
@Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
[1] as we've upgraded the guava lib for all Karaf projects to it's
latest version (KARAF-1207 [2]). With version 2.4.0 not available right
now (and with no final release date) I've created a new v2.3.x branch on
pax-exam and backported PAXEXAM-351 [1] there. Using this patch fixes
our problems.
I will like to release Pax Exam 2.3.1 on monday/thuesday with this
patch. Though there had been various other bugfixes on master (well, at
least I assume that those had been bugfixes by reading the issues and
the changesets :-)). I'm not quite sure which ones though. @Harald
and/or Toni: do you consider any of them critical for backporting to
2.3.1? If not I'll simply release with the single fix; though I think
it's a good time to stabilze 2.3.x with what we've learned during the
2.4.x development.
Kind regards,
Andreas
[1] http://team.ops4j.org/browse/PAXEXAM-351
[2] https://issues.apache.org/jira/browse/KARAF-1207
Re: Preparing Pax Exam 2.3.1 release
Posted by "Jamie G." <ja...@gmail.com>.
Andreas' latest update to
https://issues.apache.org/jira/browse/KARAF-1207 indicates that 2.4.0
may work for us, in which case
http://team.ops4j.org/browse/PAXEXAM-353 could be closed as 'won't
fix' (or the like).
Cheers,
Jamie
On Fri, Feb 17, 2012 at 6:18 AM, Toni Menzel <to...@okidokiteam.com> wrote:
> On Fri, Feb 17, 2012 at 6:55 AM, Andreas Pieber <an...@gmail.com> wrote:
>
>> Hey Guys,
>>
>> @Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
>> [1] as we've upgraded the guava lib for all Karaf projects to it's latest
>> version (KARAF-1207 [2]). With version 2.4.0 not available right now (and
>> with no final release date) I've created a new v2.3.x branch on pax-exam
>> and backported PAXEXAM-351 [1] there. Using this patch fixes our problems.
>>
>> I will like to release Pax Exam 2.3.1 on monday/thuesday with this patch.
>> Though there had been various other bugfixes on master (well, at least I
>> assume that those had been bugfixes by reading the issues and the
>> changesets :-)). I'm not quite sure which ones though. @Harald and/or Toni:
>> do you consider any of them critical for backporting to 2.3.1? If not I'll
>> simply release with the single fix; though I think it's a good time to
>> stabilze 2.3.x with what we've learned during the 2.4.x development.
>>
>>
> Is 2.4.0 not an option for you ? With exam being "tool" that is usually not
> shipped with other product releases i'd like the single, forward going
> release line. I am not into that 2.4.0 line, so need to wait for Haralds
> comments here.
> @Karaf: Is 2.4.0.RC1 okay for you - feature wise ?
>
>
>
>
>
>> Kind regards,
>> Andreas
>>
>> [1] http://team.ops4j.org/browse/**PAXEXAM-351<http://team.ops4j.org/browse/PAXEXAM-351>
>> [2] https://issues.apache.org/**jira/browse/KARAF-1207<https://issues.apache.org/jira/browse/KARAF-1207>
>>
>
>
>
> --
> Toni Menzel Source <http://tonimenzel.com>
Re: Preparing Pax Exam 2.3.1 release
Posted by Toni Menzel <to...@okidokiteam.com>.
On Fri, Feb 17, 2012 at 6:55 AM, Andreas Pieber <an...@gmail.com> wrote:
> Hey Guys,
>
> @Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
> [1] as we've upgraded the guava lib for all Karaf projects to it's latest
> version (KARAF-1207 [2]). With version 2.4.0 not available right now (and
> with no final release date) I've created a new v2.3.x branch on pax-exam
> and backported PAXEXAM-351 [1] there. Using this patch fixes our problems.
>
> I will like to release Pax Exam 2.3.1 on monday/thuesday with this patch.
> Though there had been various other bugfixes on master (well, at least I
> assume that those had been bugfixes by reading the issues and the
> changesets :-)). I'm not quite sure which ones though. @Harald and/or Toni:
> do you consider any of them critical for backporting to 2.3.1? If not I'll
> simply release with the single fix; though I think it's a good time to
> stabilze 2.3.x with what we've learned during the 2.4.x development.
>
>
Is 2.4.0 not an option for you ? With exam being "tool" that is usually not
shipped with other product releases i'd like the single, forward going
release line. I am not into that 2.4.0 line, so need to wait for Haralds
comments here.
@Karaf: Is 2.4.0.RC1 okay for you - feature wise ?
> Kind regards,
> Andreas
>
> [1] http://team.ops4j.org/browse/**PAXEXAM-351<http://team.ops4j.org/browse/PAXEXAM-351>
> [2] https://issues.apache.org/**jira/browse/KARAF-1207<https://issues.apache.org/jira/browse/KARAF-1207>
>
--
Toni Menzel Source <http://tonimenzel.com>
Re: Preparing Pax Exam 2.3.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Of course, no problem.
Regards
JB
On 02/17/2012 08:38 AM, Andreas Pieber wrote:
> Hey JB,
>
> Yeah, I've seen this. If I revert the change, upgrade to pax-exam
> 2.3.1-SNAPSHOT and use the v2.3.x branch I get at least the same errors
> as on the current master; btw am I the only one with those:
>
> Failed tests:
> testInstallCommand:CoreTest.testInstallCommand:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/3.0.0-SNAPSHOT\/zip}(org.apache.karaf.shell.itests.CoreTest):
> org.sonatype.aether.util.artifact.DefaultArtifact
> testFeatures:FeaturesTest.testFeatures:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/3.0.0-SNAPSHOT\/zip}(org.apache.karaf.shell.itests.FeaturesTest):
> Command not found: obr:list-url
>
> I'll let it be right now and upgrade/revert on trunk ASAP we release
> 2.3.1 of pax-exam. I think we can live with the old guava version quite
> good for 4 days; at least better than with another snapshot version :-)
>
> Kind regards,
> Andreas
>
> On 02/17/2012 08:02 AM, Jean-Baptiste Onofré wrote:
>> +1
>>
>> FYI, on Karaf trunk, I have rollback to Guava 10.0.1 waiting for the
>> pax-exam fix.
>>
>> Regards
>> JB
>>
>> On 02/17/2012 06:55 AM, Andreas Pieber wrote:
>>> Hey Guys,
>>>
>>> @Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
>>> [1] as we've upgraded the guava lib for all Karaf projects to it's
>>> latest version (KARAF-1207 [2]). With version 2.4.0 not available right
>>> now (and with no final release date) I've created a new v2.3.x branch on
>>> pax-exam and backported PAXEXAM-351 [1] there. Using this patch fixes
>>> our problems.
>>>
>>> I will like to release Pax Exam 2.3.1 on monday/thuesday with this
>>> patch. Though there had been various other bugfixes on master (well, at
>>> least I assume that those had been bugfixes by reading the issues and
>>> the changesets :-)). I'm not quite sure which ones though. @Harald
>>> and/or Toni: do you consider any of them critical for backporting to
>>> 2.3.1? If not I'll simply release with the single fix; though I think
>>> it's a good time to stabilze 2.3.x with what we've learned during the
>>> 2.4.x development.
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> [1] http://team.ops4j.org/browse/PAXEXAM-351
>>> [2] https://issues.apache.org/jira/browse/KARAF-1207
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Preparing Pax Exam 2.3.1 release
Posted by Andreas Pieber <an...@gmail.com>.
Hey JB,
Yeah, I've seen this. If I revert the change, upgrade to pax-exam
2.3.1-SNAPSHOT and use the v2.3.x branch I get at least the same errors
as on the current master; btw am I the only one with those:
Failed tests:
testInstallCommand:CoreTest.testInstallCommand:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/3.0.0-SNAPSHOT\/zip}(org.apache.karaf.shell.itests.CoreTest):
org.sonatype.aether.util.artifact.DefaultArtifact
testFeatures:FeaturesTest.testFeatures:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/3.0.0-SNAPSHOT\/zip}(org.apache.karaf.shell.itests.FeaturesTest):
Command not found: obr:list-url
I'll let it be right now and upgrade/revert on trunk ASAP we release
2.3.1 of pax-exam. I think we can live with the old guava version quite
good for 4 days; at least better than with another snapshot version :-)
Kind regards,
Andreas
On 02/17/2012 08:02 AM, Jean-Baptiste Onofré wrote:
> +1
>
> FYI, on Karaf trunk, I have rollback to Guava 10.0.1 waiting for the
> pax-exam fix.
>
> Regards
> JB
>
> On 02/17/2012 06:55 AM, Andreas Pieber wrote:
>> Hey Guys,
>>
>> @Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
>> [1] as we've upgraded the guava lib for all Karaf projects to it's
>> latest version (KARAF-1207 [2]). With version 2.4.0 not available right
>> now (and with no final release date) I've created a new v2.3.x branch on
>> pax-exam and backported PAXEXAM-351 [1] there. Using this patch fixes
>> our problems.
>>
>> I will like to release Pax Exam 2.3.1 on monday/thuesday with this
>> patch. Though there had been various other bugfixes on master (well, at
>> least I assume that those had been bugfixes by reading the issues and
>> the changesets :-)). I'm not quite sure which ones though. @Harald
>> and/or Toni: do you consider any of them critical for backporting to
>> 2.3.1? If not I'll simply release with the single fix; though I think
>> it's a good time to stabilze 2.3.x with what we've learned during the
>> 2.4.x development.
>>
>> Kind regards,
>> Andreas
>>
>> [1] http://team.ops4j.org/browse/PAXEXAM-351
>> [2] https://issues.apache.org/jira/browse/KARAF-1207
>
Re: Preparing Pax Exam 2.3.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
FYI, on Karaf trunk, I have rollback to Guava 10.0.1 waiting for the
pax-exam fix.
Regards
JB
On 02/17/2012 06:55 AM, Andreas Pieber wrote:
> Hey Guys,
>
> @Karaf we're currently using Pax Exam 2.3.0 and experienced PAXEXAM-351
> [1] as we've upgraded the guava lib for all Karaf projects to it's
> latest version (KARAF-1207 [2]). With version 2.4.0 not available right
> now (and with no final release date) I've created a new v2.3.x branch on
> pax-exam and backported PAXEXAM-351 [1] there. Using this patch fixes
> our problems.
>
> I will like to release Pax Exam 2.3.1 on monday/thuesday with this
> patch. Though there had been various other bugfixes on master (well, at
> least I assume that those had been bugfixes by reading the issues and
> the changesets :-)). I'm not quite sure which ones though. @Harald
> and/or Toni: do you consider any of them critical for backporting to
> 2.3.1? If not I'll simply release with the single fix; though I think
> it's a good time to stabilze 2.3.x with what we've learned during the
> 2.4.x development.
>
> Kind regards,
> Andreas
>
> [1] http://team.ops4j.org/browse/PAXEXAM-351
> [2] https://issues.apache.org/jira/browse/KARAF-1207
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com