Thread: JBPatch
View Single Post
Old 10-12-2012, 06:37 AM   #822
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by arikfunke View Post
Thanks for the extensive explanation. As far as I can tell, K3 does not use OSGi. (Maybe somebody can confirm this?)

If that is indeed the case, I imagine, the JBPatch code would require some more extensive adaptation for the patching class loader to work on K3, right?

In case it helps, on K3 the framework is started as follows:
- - - snip - - -
Which looks to be an excerpt from the attachment to post 817 above.

Except that in the actual script, the jar search is restricted to three directories, not what was used to produce the list snipped from this quote.
knc1 is offline   Reply With Quote