Any OSGi veterans willing to assist with JGDMS support for OSGi during the
modular restructure?
I've added OSGi manifests to modules, but I also need to add classpath manifest
entry's for non osgi application compatibility, I'm using the bnd-maven-plugin
to generate the OSGi manifests.
I also
I think it might make sense to go modular first, I'm a long way along that path
already with JGDMS. I could use some help.
It's worth remembering the qa and jtreg test suites combined, are very
comprehensive as these, like java, were designed to test specification
compliance of third party
I think integrating back as you go along would make more sense, but the
real issue is getting more people actively involved in the development.
I am not the right person for that - not knowing enough about
River-in-practice. Indeed, I would be very happy to turn over the PMC chair.
On an
Which changes (a subset) would you consider voting for in an Apache Release?
Is it possible more of these features could be integrated over time?
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Patricia Shanahan
Sent:
N.B. I've added equivalent methods using MarshalledInstance in a backward
compatible manner and deprecated uses of MarshalledObject in the api, with the
exception of activation constructors, however, even in these cases, it's
possible to convert MarshalledInstance to MarshalledObject and back