+1
Regards
Felix
Am 18.12.2012 um 11:37 schrieb Clement Escoffier:
> Hi,
>
> It's time to cut a release of the runtime project (1.8.6).
>
> This releases contains:
> * iPOJO Core 1.8.6
> * iPOJO Composite 1.8.6
> * iPOJO Annotations 1.8.6
> * iPOJO Runtime Project 1.8.6
>
> Those releases con
+1
Carsten
2012/12/20 Felix Meschberger :
> +1
>
> Regards
> Felix
>
> Am 18.12.2012 um 11:37 schrieb Clement Escoffier:
>
>> Hi,
>>
>> It's time to cut a release of the runtime project (1.8.6).
>>
>> This releases contains:
>> * iPOJO Core 1.8.6
>> * iPOJO Composite 1.8.6
>> * iPOJO Annotations
[
https://issues.apache.org/jira/browse/FELIX-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-3810:
---
Assignee: Carsten Ziegeler
> @org.osgi.service.component.annotations.Component co
[
https://issues.apache.org/jira/browse/FELIX-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-3810:
Component/s: (was: Maven SCR Plugin)
SCR Annotations
> @org.osgi.s
[
https://issues.apache.org/jira/browse/FELIX-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-3810.
-
Resolution: Fixed
Thanks for your patch, I've applied it
> @org.osgi.ser
Florent BENOIT created FELIX-3827:
-
Summary: Error in bbd-ipojo-plugin of manipulating jar with
embedded dependencies with maven bundle plugin + bnd-ipojo-plugin
Key: FELIX-3827
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/FELIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent BENOIT updated FELIX-3827:
--
Attachment: ipojo.bug.tgz
Maven project used to reproduce the issue
> Error in
[
https://issues.apache.org/jira/browse/FELIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Sauthier reassigned FELIX-3827:
-
Assignee: Guillaume Sauthier
> Error in bbd-ipojo-plugin of manipulating jar
[
https://issues.apache.org/jira/browse/FELIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Sauthier updated FELIX-3827:
--
Affects Version/s: ipojo-manipulator-1.8.6
Reproduced with ipojo-bnd-plugin version 1.8
Hi,
I've commited a first implementation in my sandbox. Besides from
adding new interfaces (which I think need some more work especially
the attachment handling), this bundle registers a web console plugin
for the configuration status.
All new status providers are registered as console plugins und
[
https://issues.apache.org/jira/browse/FELIX-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533595#comment-13533595
]
Henry Saginor edited comment on FELIX-3799 at 12/20/12 5:22 PM:
I am using Gemini JPA along with EclipseLink on Apache Felix, and I can
reproduce a deadlock at will. Here's what happens:
- Gemini JPA gets installed.
- My bundle which includes persistence entities is installing.
- Gemini JPA gets notification about my bundle's status change
- Gemini JPA scans t
On 12/20/12 14:43 , Jad Naous wrote:
I am using Gemini JPA along with EclipseLink on Apache Felix, and I can
reproduce a deadlock at will. Here's what happens:
- Gemini JPA gets installed.
- My bundle which includes persistence entities is installing.
- Gemini JPA gets notification about my bund
If a bundle undergoes a refresh while ipojo is still initializing
components, a deadlock can happen. The issue is that if ipojo is
attempting to register a service, it will be doing it while synchronizing
on the InstanceCreator instance. It will then try to register a service
which requires the fr
Coming up...
On Thu, Dec 20, 2012 at 11:51 AM, Richard S. Hall wrote:
> nto the installing thread until the refresh is done? If so, that sounds
> like the issue to me. Assuming Gemini JPA is using a synchronous bundle
> listener to get the bundle state change event, it shouldn't turn around and
>
Hmm, now I can't reproduce that anymore. All I can reproduce is the IPOJO
deadlock problem I started another thread on. Maybe I confused that problem
for this... Sorry to bother. I'll post again if I can reproduce and
immediately capture stack traces...
Thanks,
Jad.
On Thu, Dec 20, 2012 at 1:23
On 12/20/12 4:10 PM, Jad Naous wrote:
If a bundle undergoes a refresh while ipojo is still initializing
components, a deadlock can happen. The issue is that if ipojo is
attempting to register a service, it will be doing it while synchronizing
on the InstanceCreator instance. It will then try to
It does look like the same issue.
Got the trunk/framework. mvn clean install gives:
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
org.apache.felix.framework ---
Dec 20, 2012 3:54:59 PM org.sonatype.guice.bean.reflect.Logs$JULSink warn
WARNING: Error injecting: org.apache.mave
On 12/20/12 6:56 PM, Jad Naous wrote:
It does look like the same issue.
Got the trunk/framework. mvn clean install gives:
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
org.apache.felix.framework ---
Dec 20, 2012 3:54:59 PM org.sonatype.guice.bean.reflect.Logs$JULSink warn
W
19 matches
Mail list logo
