t;
> Re: Subsystems proxy dependency version
>
> Actually, further to this, I've just done a bit more looking, and
> there are a few sub-1.0.0 dependencies in the subsystem code which
> will need to be moved to the 1.0.0 versions before the subsystems
> bundles will be able to w
If I understand correctly, all of the dependencies listed below should
point to version 1.0.0, but proxy should remain at 1.0.1[-SNAPSHOT]?
John
>
> Re: Subsystems proxy dependency version
>
> Actually, further to this, I've just done a bit more looking, and
> there
Thanks Mark. I just wanted to make sure it was needed, which it is, so
that's great.
On 1 Sep 2012, at 15:18, Mark Nuttall wrote:
Hi Holly,
I recently made that change to the proxy code. I think it was under
Aries-909. I've added some metadata to the Proxy weaving hook that
declares
the pa
Hi Holly,
I recently made that change to the proxy code. I think it was under
Aries-909. I've added some metadata to the Proxy weaving hook that declares
the packages that it weaves: the subsystem runtime needs this information.
The first subsystem release will need an accompanying release of proxy
Actually, further to this, I've just done a bit more looking, and
there are a few sub-1.0.0 dependencies in the subsystem code which
will need to be moved to the 1.0.0 versions before the subsystems
bundles will be able to work with the recently released Aries bundles.
They didn't get updated autom
When I was looking at the builds, I noticed that the subsystem itests
depend on proxy-1.0.1-SNAPSHOT, rather than proxy-1.0.0. Is there
something in the 1.0.1 proxy which the subsystem tests need, John? If
not it would be better to depend on the released version of the proxy
bundle, 1.0.0. This avo
