Awesome...thanks.
I almost committed the change myself, but like I said...I was only
*mostly* sure...not fully sure. I suppose that I could've done it and if
it caused anybody else any grief, they could back it out.
Regarding the hooks: That's what I suspected...thanks for confirming.
Alin Dreghiciu wrote:
I checked and indeed now they depend on Spring 1.2. By the moment I
made the profile, the dependency was on 1.1.2.
I committed the change as I already changed the profile for testing,
but in the future when you are sure about a think like this go ahead
and commit.
The hooks must be implemented by the framework so I do not think there
is an extra bundle from equinox that does just that (but you never
know). And they will have that only in the upcoming release 3.5.
I suggest that you use --p=e --v=latest to get the latest equinox.
On Mon, Apr 6, 2009 at 6:26 AM, Craig Walls <[email protected]> wrote:
I'm playing around some more with the new Pax Runner 0.18.0-SNAPSHOT
profiles and just tried the cxf.dosgi profile. It looks as if it needs to
pull in Spring-DM 1.2.0 (not 1.1.2 as it does now). I don't mind committing
the change to the composite file myself, but...I just wanted to make sure
that I'm seeing this right before I make the change.
If I start it with pax-run.sh --profiles=cxf.dosgi
scan-composite:mvn:org.ops4j.pax.runner.profiles/spring.dm/1.2.0/compos...@2,
it seems to work fine (albeit, I get two versions of Spring-DM installed).
Also...it appears that it only works in Felix. In Equinox, the
"cxf-dosgi-ri-dsw-cxf_1.0.0.SNAPSHOT" bundle won't start because it needs
org.osgi.framework.hooks.service. Is there an Equinox-equivalent bundle that
has that package?
Anybody else see the same thing?
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
