Hi,
I don't have an explanation for this. I know at some point I had my
subsystem-core pointing to 3.7.0.v20110221 and fixed some consequent
compile errors. Some of these are in the original patch. However, after
seeing your email, I discovered my subsystem-core was pointing back to the
old version. After changing it again, I received compile errors on one
class, SubsystemResourceProcessor. I attached a patch for this on the bug
you opened.
Thanks,
John
Jeremy Hughes
<[email protected]
rg> To
Sent by: [email protected]
[email protected] cc
om
Subject
Re: Aries Subsystem
03/10/2011 12:05
PM
Please respond to
[email protected].
org
Hi John, welcome :-)
I've been having trouble building subsystem since the changes in your
patch and I just wonder whether everything was correct and present.
First up was the subsystem/pom.xml was using Felix bundlerepository
1.6.1-SNAPSHOT and those can't be found now because the latest release
is 1.6.4. This is probably nothing to do with your changes and more to
do with me having a clean .m2 local repo without a 1.6.1-SNAPSHOT in
it. So I moved up to 1.6.4.
Then it seems subsystem/subsystem-core/pom.xml is using a different
Equinox build (3.7.0.v20110110) to the poms in subsystem-itests
-scope-impl and -scope-itests (3.7.0.v20110221). If I move the -core
pom to use the newer Equinox level (so the levels are consistent) then
I get a compile problem - the org.osgi.framework.wiring.Capability
class is being used - which is no longer present in the Equinox
bundle. There's a BundleCapability but that's quite different I think.
I opened a JIRA - ARIES-606 to fix this. Is there something you hadn't
included in your patch?
Many thanks,
Jeremy
On 3 March 2011 00:26, John W Ross <[email protected]> wrote:
>
>
> Hello,
>
> I would like to help with moving the Aries Subsystem implementation
> forward. I work at IBM and participate in the EEG and CPEG groups. I've
> also been consulting with the Subsystem spec lead, Graham Charters, for
the
> past few weeks. I wanted to introduce myself because I will be providing
a
> patch that updates the implementation to the released version of OSGi
core
> 4.3. This required numerous, low level changes that had cascading affects
> across several projects, so the patch is not small. I also added a number
> of additional tests requiring several configuration changes.
>
> Thanks,
> John
