[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [virgo-dev] Virgo deployment
|
Hi Scott,
You got it right. We are indeed trying to enable p2 provisioning for Virgo, so that you could install Virgo from scratch or provision Virgo on top of an existing Equinox using p2. The part with the launcher is mostly involved to enable the whole p2 stuff in the first place, by removing fixed startup order dependencies, and to give Virgo more flexibility - it should not depend on a specific launcher. That would enable for example proper usage of simple configurator.
Are you looking to provision ECF on top of Virgo using p2?
Best Regards
Borislav
2011/1/18 Scott Lewis
<slewis@xxxxxxxxxxxxx>
Question: I would like to install some configuration of Virgo (and dependencies) into an existing equinox/osgi server using p2. I understand that Virgo is in the process of moving to using the Equinox launcher (i.e. the Rationale for Virgo launcher thread as I understand it), and I think (although I'm not sure of this), that at some point the Virgo project will create/publish some features (although I can/could create these myself) that could be installed into an existing framework using p2. Is this (installing Virgo itself using p2+features) where things are headed?...or am I misinterpreting the work that's going on with the launcher and other things?
The reason I ask: the ECF project has several consumers that have expressed interest in using both Spring/Virgo along with ECF remote services [1], and soon (ECF 3.5...late feb) with ECF's implementation of the OSGi 4.2 remote service admin (RSA) specification [2].
Thanksinadvance for any clarification,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=302113
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=324215
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
