Hendy Irawan created FELIX-3598:
---
Summary: framework.resolver.ResolverImpl.toStringBlame throws
NullPointerException on jBPM-bpmn2 5.3.0.Final activator
Key: FELIX-3598
URL:
[
https://issues.apache.org/jira/browse/FELIX-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hendy Irawan updated FELIX-3598:
Description:
Reference:
* https://issues.jboss.org/browse/JBPM-3715
*
[
https://issues.apache.org/jira/browse/FELIX-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414600#comment-13414600
]
Hendy Irawan commented on FELIX-3598:
-
Workaround : Replacing Karaf's felix framework
[
https://issues.apache.org/jira/browse/FELIX-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-3598.
--
Resolution: Not A Problem
Since this is fixed by a later version of the framework, then we
Hi,
Would it be possible/within the spec if, when deploying a boot class
path fragment bundle, for Felix to install the bundle and keep it at
the INSTALLED state and not move it to the RESOLVED state? This is to
actually install the bundle and refuse to change it to RESOLVED,
instead of refusing
On 7/15/12 16:35 , Lucas Galfaso wrote:
Hi,
Would it be possible/within the spec if, when deploying a boot class
path fragment bundle, for Felix to install the bundle and keep it at
the INSTALLED state and not move it to the RESOLVED state? This is to
actually install the bundle and refuse to
Hi,
My comments inline.
On Sun, Jul 15, 2012 at 5:56 PM, Richard S. Hall he...@ungoverned.org wrote:
On 7/15/12 16:35 , Lucas Galfaso wrote:
Hi,
Would it be possible/within the spec if, when deploying a boot class
path fragment bundle, for Felix to install the bundle and keep it at
[
https://issues.apache.org/jira/browse/FELIX-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414858#comment-13414858
]
Hendy Irawan commented on FELIX-3598:
-
Thank you Richard.
One question, the latest
