Hi
I have reported FELIX-4695 [1] with two potential patches. I think the Felix
class patch is correct, while the ExtensionManager patch is probably sufficient
for this problem.
I would prefer to patch the Felix class at the expense of the
org.osgi.framework.os.version property not exposing th
Hi
Ok, there seems to be a larger problem to this, it seems.
The ExtensionManager creates native capabilities in the
ExtensionManager.buildNativeCapabilites() method. This method gets the
PROCESSOR, OS_NAME, and OS_VERSION framework properties to build this
capability.
On the other hand the R
Hi Felix,
You are correct; it looks like the ExtensionManager is trying to parse my
os version.
In the initial mail I sent, I attached the logs, but it seems that @dev
list does like attachments ?
Here is a copy/past of the compile error logs (i don't have applied your
patch from the FELIX-4692 i
Hi
I can reproduce this. And worse still, it actually prevents the framework from
starting under Linux.
The situation is that the ExtensionManager wants to parse the os.version system
property into an OSGi Version. the os.version seems to be based on the kernel
version, which in my case of Ubu
Hi Pierre,
I don't see your attachment with the errors. Did you forget to attach it?
Cheers,
David
On 12 November 2014 13:49, Pierre De Rop wrote:
> Hello everyone;
>
> I would like to test the patch provided by Felix for the FELIX-4692 issue
> ("Improve Service access time").
> But before app
Hello everyone;
I would like to test the patch provided by Felix for the FELIX-4692 issue
("Improve Service access time").
But before applying the patch provided by Felix, I just can't compile the
framework (the tests does not seem to compile):
I'm on a linux fc19,
uname -a = Linux nx0012 3.14.22
