Hi Andreas,
that's actually what I had in mind when creating this jira :)
so let's go ahead and copy the jre7 part and tweak in constantly when we
get better knowledge :)
Concerning the wrapper, I think doing a crosscompile (or do we have a arm
based build server at apache?)
could be worth
Hi Robert,
very interesting, thanks for the sharing.
FYI, I'm upgrading jre.properties in both Karaf 2.3.x and trunk.
Regards
JB
On 2013-02-06 23:07, Robert Murphy wrote:
Greetings!
I managed to get Karaf running smoothly on the Raspberry Pi against
the Sun JDK 8 Preview; I'd love to work
I am able to resolve it by having below Dynamic-Import in my MANIFEST.MF
file.
DynamicImport-Package:
org.apache.karaf.jaas.boot.principal;version=[2.3,3),org.apache.karaf.jaas.config;version=[2.3,3),
org.eclipse.jetty.plus.jaas;version=[7.1.0,8.0.0)
--
View this message in context:
@Robert: JRE properties had been pushed (thanks JB)
@JB: Do you think we can cross compiile the wrapper scripts for ARM the
same way you've done for windows 64 bit?
Kind regards,
Andreas
On Thu, Feb 7, 2013 at 9:39 AM, j...@nanthrax.net wrote:
Hi Robert,
very interesting, thanks for the
Hi Andreas,
It should be possible to cross compile on ARM for Tanuki JSW.
We can create a Jira about that and I can tackle that.
AFAIR, commons-daemon provides ARM support by default.
Regards
JB
On 2013-02-07 11:47, Andreas Pieber wrote:
@Robert: JRE properties had been pushed (thanks JB)
So the idea should rather be to completely change to commons-deamon instead
of the current approach for the wrapper bundle?
Kind regards,
Andreas
On Thu, Feb 7, 2013 at 11:57 AM, j...@nanthrax.net wrote:
Hi Andreas,
It should be possible to cross compile on ARM for Tanuki JSW.
We can
Hi Andreas,
it might be a good reason to think about.
Maybe we should start a new discussion thread about that topic. :)
regards, Achim
2013/2/7 Andreas Pieber anpie...@gmail.com
So the idea should rather be to completely change to commons-deamon
instead of the current approach for the
+1
for changing to commons-daemon. If we decide to change I am willing to
help with the changes.
Christian
On 07.02.2013 12:21, Andreas Pieber wrote:
So the idea should rather be to completely change to commons-deamon
instead of the current approach for the wrapper bundle?
Kind regards,
As I said long time ago ;), I already have the commons-daemon module
ready for the trunk.
Anyway, my point is that we can do both: cross compile for JSW (at
least for Karaf 2.3.x), commons-daemon for trunk (and leave the choice
between commons-daemon and JSW).
Regards
JB
On 2013-02-07
Ok,
so we do have a fully functional wrapper based on commons-deamon at hand
but don't use it (yet).
We should start a vote to switch to it for trunk and maybe do a
ARM cross-compile for 2.3.
regards, Achim
2013/2/7 j...@nanthrax.net
As I said long time ago ;), I already have the
Agree,
my proposal would be:
- keep JSW as it is for Karaf 2.3.1 and 3.0.0.RC1
- provide ARM support (by cross compilation) in Karaf 2.3.2 and 3.0.1
- provide commons-daemon support in Karaf 2.4.0 and 3.1.0
Regards
JB
On 2013-02-07 13:20, Achim Nierbeck wrote:
Ok,
so we do have a fully
I propose to simply switch to commons daemon for karaf 3.1 and do no
changes for earlier versions.
So this means ARM support is a bit delayed but it is a lot less work.
Christian
On 07.02.2013 13:28, j...@nanthrax.net wrote:
Agree,
my proposal would be:
- keep JSW as it is for Karaf 2.3.1
It works for me as well.
Regards
JB
On 2013-02-07 13:39, Christian Schneider wrote:
I propose to simply switch to commons daemon for karaf 3.1 and do no
changes for earlier versions.
So this means ARM support is a bit delayed but it is a lot less work.
Christian
On 07.02.2013 13:28,
I second Christian here; ARM support would be funny and cool but I
don't see any requirement to add it anywhere else than 3.1. If there's a
strong requirement we can backport it, but I don't expect any :-)
Kind regards,
Andreas
On Thu, Feb 7, 2013 at 1:39 PM, Christian Schneider
Hoping someone can help with this one. We're using Karaf 2.2.9 and we recently
enabled https. Now everytime someone connects to the https port using IE, we
see *tons* of stack traces coming from Jetty on the console like this one:
org.eclipse.jetty.io.EofException
at
Hello,
I am currently encounter an issue where one my UI bundle hang %50 at
'GracePeriod' and never recover at first time ever started. here is
the log
2013-02-07 20:09:19,280 | INFO | lixDispatchQueue |
PaxWicketBundleListener | extender.PaxWicketBundleListener
58 | 160 -
by default, the bundle should bail out after 5 min, but it hangs that
state forever. Sound like blueprint bug?
I am using karaf 2.3.0 java 1.7
-D
17 matches
Mail list logo
