You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2015/10/10 00:07:43 UTC
[VOTE] Apache Karaf 4.0.2 release
Hi all,
I submit Apache Karaf 4.0.2 to your vote:
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
Git tag:
karaf-4.0.2
Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1048/
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)
This vote will be open for at least 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
AW: [VOTE] Apache Karaf 4.0.2 release
Posted by Roedl Lukas <Lu...@ait.ac.at>.
+1 (non-binding)
regards,
Lukas
-----Ursprüngliche Nachricht-----
Von: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
Gesendet: Samstag, 10. Oktober 2015 00:08
An: Karaf Dev
Betreff: [VOTE] Apache Karaf 4.0.2 release
Hi all,
I submit Apache Karaf 4.0.2 to your vote:
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
Git tag:
karaf-4.0.2
Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1048/
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)
This vote will be open for at least 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Christian Schneider <ch...@die-schneider.net>.
I agree.
Christian
On 12.10.2015 10:51, Achim Nierbeck wrote:
> I'd rather keep this vote open as it seems like to be a corner case which
> can be addressed with a 4.0.3 which we can shortly after the aries bug in
> JPA is fixed.
>
> regards, Achim
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
I'd rather keep this vote open as it seems like to be a corner case which
can be addressed with a 4.0.3 which we can shortly after the aries bug in
JPA is fixed.
regards, Achim
2015-10-11 21:10 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> By the way, I upgraded to new Blueprint release for 4.0.2 (as it fixed
> couple of "important" issues). I will take a look and a diff between the
> two versions.
>
> Regards
> JB
>
> On 10/11/2015 08:18 PM, Christian Schneider wrote:
>
>> I think that I found the problem.
>>
>> When the blueprint context is created the future for the timeout of
>> dependencies is canceled.
>>
>> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L379
>>
>>
>> In Aries JPA I use a ComponentDefinitionRegistryProcessor to scan for
>> the @PersistenceContext annoations and register a service reference for
>> these. I think that this triggers
>> the future for the timeout of such dependencies again. If this processor
>> is called after the future is canceled above then the future will not be
>> canceled anymore. So after the timeout (5min) it will
>> trigger and stop the blueprintcontainer even if all dependencies are
>> satisfied now.
>>
>> This is the code that is executed after the timeout:
>>
>> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L341
>>
>>
>> It matches the exception and explains why there are no unresolved
>> dependencies.
>>
>> I would be happy about feedback from anyone with deeper blueprint
>> knowledge. Is what I do there in Aries JPA incorrect? If yes then we
>> need a new Aries JPA release .. though I am not sure how to better
>> address the problem.
>> If it is correct then we need to fix this in blueprint core.
>> A simple fix/workaround would be to check if there are no unresolved
>> dependencies when the future times out and not stop the container in
>> this case. A better fix would cancel the future as soon as all
>> dependencies are fulfilled.
>>
>> In any case I propose we cancel the release and try to include a fix in
>> karaf 4.0.2. So I revert my vote to
>>
>> -1 (non binding)
>>
>> Christian
>>
>> On 11.10.2015 19:24, Christian Schneider wrote:
>>
>>> I just did some more testing and found a problem.
>>>
>>> When I run my tasklist-blueprint-cdi example it works fine at the
>>> start but after some time I see this exception:
>>> 2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 |
>>> BlueprintContainerImpl | 12 -
>>> org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint
>>> container for bundle
>>> net.lr.tasklist.cdi.tasklist-persistence/1.0.0.SNAPSHOT due to
>>> unresolved dependencies []
>>> java.util.concurrent.TimeoutException
>>> at
>>>
>>> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[12:org.apache.aries.blueprint.core:1.4.4]
>>>
>>> at
>>>
>>> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[12:org.apache.aries.blueprint.core:1.4.4]
>>>
>>> at
>>>
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
>>>
>>> at
>>> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
>>> at
>>>
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_60]
>>>
>>> at
>>>
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_60]
>>>
>>> at
>>>
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
>>>
>>> at
>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
>>>
>>> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
>>>
>>> After this the tasklist-persistence bundle does not work anymore. If
>>> this does not only happen with my example then it would be a pretty
>>> critical bug.
>>>
>>> I am not yet sure what the reason is but I will dig some more. I think
>>> the problem could be either in blueprint core or in blueprint jpa.
>>>
>>> If you want to test yourself you should use the branch jpa-2.1.0 (old
>>> name ... it uses jpa 2.2.0 now).
>>>
>>> https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi
>>>
>>>
>>>
>>> Christian
>>>
>>>
>>> On 11.10.2015 16:53, Christian Schneider wrote:
>>>
>>>> +1 (non binding)
>>>>
>>>> Tested my blueprint and DS examples (jpa,transaction, hibernate,
>>>> cxf, jaxrs-connector)
>>>>
>>>> Looks all good.
>>>>
>>>> Christian
>>>>
>>>
>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
By the way, I upgraded to new Blueprint release for 4.0.2 (as it fixed
couple of "important" issues). I will take a look and a diff between the
two versions.
Regards
JB
On 10/11/2015 08:18 PM, Christian Schneider wrote:
> I think that I found the problem.
>
> When the blueprint context is created the future for the timeout of
> dependencies is canceled.
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L379
>
>
> In Aries JPA I use a ComponentDefinitionRegistryProcessor to scan for
> the @PersistenceContext annoations and register a service reference for
> these. I think that this triggers
> the future for the timeout of such dependencies again. If this processor
> is called after the future is canceled above then the future will not be
> canceled anymore. So after the timeout (5min) it will
> trigger and stop the blueprintcontainer even if all dependencies are
> satisfied now.
>
> This is the code that is executed after the timeout:
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L341
>
>
> It matches the exception and explains why there are no unresolved
> dependencies.
>
> I would be happy about feedback from anyone with deeper blueprint
> knowledge. Is what I do there in Aries JPA incorrect? If yes then we
> need a new Aries JPA release .. though I am not sure how to better
> address the problem.
> If it is correct then we need to fix this in blueprint core.
> A simple fix/workaround would be to check if there are no unresolved
> dependencies when the future times out and not stop the container in
> this case. A better fix would cancel the future as soon as all
> dependencies are fulfilled.
>
> In any case I propose we cancel the release and try to include a fix in
> karaf 4.0.2. So I revert my vote to
>
> -1 (non binding)
>
> Christian
>
> On 11.10.2015 19:24, Christian Schneider wrote:
>> I just did some more testing and found a problem.
>>
>> When I run my tasklist-blueprint-cdi example it works fine at the
>> start but after some time I see this exception:
>> 2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 |
>> BlueprintContainerImpl | 12 -
>> org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint
>> container for bundle
>> net.lr.tasklist.cdi.tasklist-persistence/1.0.0.SNAPSHOT due to
>> unresolved dependencies []
>> java.util.concurrent.TimeoutException
>> at
>> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[12:org.apache.aries.blueprint.core:1.4.4]
>>
>> at
>> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[12:org.apache.aries.blueprint.core:1.4.4]
>>
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
>>
>> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
>>
>> After this the tasklist-persistence bundle does not work anymore. If
>> this does not only happen with my example then it would be a pretty
>> critical bug.
>>
>> I am not yet sure what the reason is but I will dig some more. I think
>> the problem could be either in blueprint core or in blueprint jpa.
>>
>> If you want to test yourself you should use the branch jpa-2.1.0 (old
>> name ... it uses jpa 2.2.0 now).
>> https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi
>>
>>
>>
>> Christian
>>
>>
>> On 11.10.2015 16:53, Christian Schneider wrote:
>>> +1 (non binding)
>>>
>>> Tested my blueprint and DS examples (jpa,transaction, hibernate,
>>> cxf, jaxrs-connector)
>>>
>>> Looks all good.
>>>
>>> Christian
>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I would prefer keep the release as it is and fix for 4.0.3, else it
means that 4.0.2 will be postponed for a long time (as we would maybe
need a new Aries Blueprint release).
Moreover, I'm not sure where the problem is exactly located (probably in
Blueprint Core).
Regards
JB
On 10/11/2015 08:18 PM, Christian Schneider wrote:
> I think that I found the problem.
>
> When the blueprint context is created the future for the timeout of
> dependencies is canceled.
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L379
>
>
> In Aries JPA I use a ComponentDefinitionRegistryProcessor to scan for
> the @PersistenceContext annoations and register a service reference for
> these. I think that this triggers
> the future for the timeout of such dependencies again. If this processor
> is called after the future is canceled above then the future will not be
> canceled anymore. So after the timeout (5min) it will
> trigger and stop the blueprintcontainer even if all dependencies are
> satisfied now.
>
> This is the code that is executed after the timeout:
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L341
>
>
> It matches the exception and explains why there are no unresolved
> dependencies.
>
> I would be happy about feedback from anyone with deeper blueprint
> knowledge. Is what I do there in Aries JPA incorrect? If yes then we
> need a new Aries JPA release .. though I am not sure how to better
> address the problem.
> If it is correct then we need to fix this in blueprint core.
> A simple fix/workaround would be to check if there are no unresolved
> dependencies when the future times out and not stop the container in
> this case. A better fix would cancel the future as soon as all
> dependencies are fulfilled.
>
> In any case I propose we cancel the release and try to include a fix in
> karaf 4.0.2. So I revert my vote to
>
> -1 (non binding)
>
> Christian
>
> On 11.10.2015 19:24, Christian Schneider wrote:
>> I just did some more testing and found a problem.
>>
>> When I run my tasklist-blueprint-cdi example it works fine at the
>> start but after some time I see this exception:
>> 2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 |
>> BlueprintContainerImpl | 12 -
>> org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint
>> container for bundle
>> net.lr.tasklist.cdi.tasklist-persistence/1.0.0.SNAPSHOT due to
>> unresolved dependencies []
>> java.util.concurrent.TimeoutException
>> at
>> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[12:org.apache.aries.blueprint.core:1.4.4]
>>
>> at
>> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[12:org.apache.aries.blueprint.core:1.4.4]
>>
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
>>
>> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
>>
>> After this the tasklist-persistence bundle does not work anymore. If
>> this does not only happen with my example then it would be a pretty
>> critical bug.
>>
>> I am not yet sure what the reason is but I will dig some more. I think
>> the problem could be either in blueprint core or in blueprint jpa.
>>
>> If you want to test yourself you should use the branch jpa-2.1.0 (old
>> name ... it uses jpa 2.2.0 now).
>> https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi
>>
>>
>>
>> Christian
>>
>>
>> On 11.10.2015 16:53, Christian Schneider wrote:
>>> +1 (non binding)
>>>
>>> Tested my blueprint and DS examples (jpa,transaction, hibernate,
>>> cxf, jaxrs-connector)
>>>
>>> Looks all good.
>>>
>>> Christian
>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Christian Schneider <ch...@die-schneider.net>.
I think that I found the problem.
When the blueprint context is created the future for the timeout of
dependencies is canceled.
https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L379
In Aries JPA I use a ComponentDefinitionRegistryProcessor to scan for
the @PersistenceContext annoations and register a service reference for
these. I think that this triggers
the future for the timeout of such dependencies again. If this processor
is called after the future is canceled above then the future will not be
canceled anymore. So after the timeout (5min) it will
trigger and stop the blueprintcontainer even if all dependencies are
satisfied now.
This is the code that is executed after the timeout:
https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java#L341
It matches the exception and explains why there are no unresolved
dependencies.
I would be happy about feedback from anyone with deeper blueprint
knowledge. Is what I do there in Aries JPA incorrect? If yes then we
need a new Aries JPA release .. though I am not sure how to better
address the problem.
If it is correct then we need to fix this in blueprint core.
A simple fix/workaround would be to check if there are no unresolved
dependencies when the future times out and not stop the container in
this case. A better fix would cancel the future as soon as all
dependencies are fulfilled.
In any case I propose we cancel the release and try to include a fix in
karaf 4.0.2. So I revert my vote to
-1 (non binding)
Christian
On 11.10.2015 19:24, Christian Schneider wrote:
> I just did some more testing and found a problem.
>
> When I run my tasklist-blueprint-cdi example it works fine at the
> start but after some time I see this exception:
> 2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 |
> BlueprintContainerImpl | 12 -
> org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint
> container for bundle
> net.lr.tasklist.cdi.tasklist-persistence/1.0.0.SNAPSHOT due to
> unresolved dependencies []
> java.util.concurrent.TimeoutException
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[12:org.apache.aries.blueprint.core:1.4.4]
> at
> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[12:org.apache.aries.blueprint.core:1.4.4]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
> at
> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
>
> After this the tasklist-persistence bundle does not work anymore. If
> this does not only happen with my example then it would be a pretty
> critical bug.
>
> I am not yet sure what the reason is but I will dig some more. I think
> the problem could be either in blueprint core or in blueprint jpa.
>
> If you want to test yourself you should use the branch jpa-2.1.0 (old
> name ... it uses jpa 2.2.0 now).
> https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi
>
>
>
> Christian
>
>
> On 11.10.2015 16:53, Christian Schneider wrote:
>> +1 (non binding)
>>
>> Tested my blueprint and DS examples (jpa,transaction, hibernate,
>> cxf, jaxrs-connector)
>>
>> Looks all good.
>>
>> Christian
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Christian Schneider <ch...@die-schneider.net>.
I just did some more testing and found a problem.
When I run my tasklist-blueprint-cdi example it works fine at the start
but after some time I see this exception:
2015-10-11 19:08:43,371 | ERROR | rint Extender: 2 |
BlueprintContainerImpl | 12 - org.apache.aries.blueprint.core
- 1.4.4 | Unable to start blueprint container for bundle
net.lr.tasklist.cdi.tasklist-persistence/1.0.0.SNAPSHOT due to
unresolved dependencies []
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[12:org.apache.aries.blueprint.core:1.4.4]
at
org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[12:org.apache.aries.blueprint.core:1.4.4]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
After this the tasklist-persistence bundle does not work anymore. If
this does not only happen with my example then it would be a pretty
critical bug.
I am not yet sure what the reason is but I will dig some more. I think
the problem could be either in blueprint core or in blueprint jpa.
If you want to test yourself you should use the branch jpa-2.1.0 (old
name ... it uses jpa 2.2.0 now).
https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-blueprint-cdi
Christian
On 11.10.2015 16:53, Christian Schneider wrote:
> +1 (non binding)
>
> Tested my blueprint and DS examples (jpa,transaction, hibernate, cxf,
> jaxrs-connector)
>
> Looks all good.
>
> Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Christian Schneider <ch...@die-schneider.net>.
+1 (non binding)
Tested my blueprint and DS examples (jpa,transaction, hibernate, cxf,
jaxrs-connector)
Looks all good.
Christian
On 10.10.2015 00:07, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
+1 (binding)
verified sources and checked various applications.
regards, Achim
2015-10-10 0:07 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Freeman Fang <fr...@gmail.com>.
+1 (binding)
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
> On Oct 10, 2015, at 6:07 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, we upgraded to support SCR 2.0.0 annotations, but being able to use
"old" annotations too.
Regards
JB
On 10/11/2015 11:32 AM, Fabian Lange wrote:
> +1, non binding
>
> I built my custom distribution, and that worked fine from the staging repo.
> thanks for fixing this annoyance. Distribution passes smoke tests as
> before, no unusual exceptions during build or startup.
>
> I noticed that my archive was bigger (about 500k compressed), I found that
> Karaf
> ships system/org/apache/servicemix/bundles/org.apache.servicemix.bundles.not-yet-commons-ssl.
> Is that intentional?
> I also noticed a bigger change in felix framework, especially scr seems to
> ship with a compat module. Is there documentation on what new features I
> can take advantage of?
>
> Fabian
>
>
> On Sat, Oct 10, 2015 at 12:07 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi all,
>>
>> I submit Apache Karaf 4.0.2 to your vote:
>>
>> Release Notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>>
>> Git tag:
>> karaf-4.0.2
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Fabian Lange <fa...@codecentric.de>.
+1, non binding
I built my custom distribution, and that worked fine from the staging repo.
thanks for fixing this annoyance. Distribution passes smoke tests as
before, no unusual exceptions during build or startup.
I noticed that my archive was bigger (about 500k compressed), I found that
Karaf
ships system/org/apache/servicemix/bundles/org.apache.servicemix.bundles.not-yet-commons-ssl.
Is that intentional?
I also noticed a bigger change in felix framework, especially scr seems to
ship with a compat module. Is there documentation on what new features I
can take advantage of?
Fabian
On Sat, Oct 10, 2015 at 12:07 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (binding)
Regards
JB
On 10/10/2015 12:07 AM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
[RESULT][VOTE] Apache Karaf 4.0.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
this vote passed with the following result:
+1 (binding): Achim Nierbeck, Jamie Goodyear, Jean-Baptiste Onofré,
Freeman Fang
+1 (non binding): Fabian Lange, Markus Rathgeb, Lukas Roedl, Christian
Schneider
I'm promoting the artifacts to central, update Jira and I will announce
the release.
Thanks all for your vote.
Regards
JB
On 10/10/2015 12:07 AM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by "Jamie G." <ja...@gmail.com>.
+1 (binding)
On Sun, Oct 11, 2015 at 8:53 AM, Markus Rathgeb <ma...@gmail.com> wrote:
> +1, non-binding
>
> Thanks a lot to all for the great work.
>
> 2015-10-10 0:07 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>> Hi all,
>>
>> I submit Apache Karaf 4.0.2 to your vote:
>>
>> Release Notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>>
>> Git tag:
>> karaf-4.0.2
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
Re: [VOTE] Apache Karaf 4.0.2 release
Posted by Markus Rathgeb <ma...@gmail.com>.
+1, non-binding
Thanks a lot to all for the great work.
2015-10-10 0:07 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi all,
>
> I submit Apache Karaf 4.0.2 to your vote:
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333259&styleName=Text&projectId=12311140
>
> Git tag:
> karaf-4.0.2
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1048/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com