No, but there is a platform property you can set on the State object to put
the resolver in development mode. Using the platform property
osgi.resolverMode=development will allow bundle constraints
(Import-Package, Require-Bundle etc.) to resolve to bundles in the state
which are not resolved
That sounds exactly like what I need. I'll give it a try.
Thanks!
On Mon, Jul 14, 2008 at 4:28 PM, Thomas Watson [EMAIL PROTECTED] wrote:
No, but there is a platform property you can set on the State object to put
the resolver in development mode. Using the platform property
I am out of the office until 07/27/2008.
I am currently in the customer site with very limited internet access so
please excuse the delay for the reply. I will be out of the office starting
July 14th, 2008 and will not return until July 27th, 2008.
Note: This is an automated response to your
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg04448.html
--
Farokh Morshed [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/08/2008 01:28 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] Will P2 ever
I did read this note before asking my question. I can't quite parse the
last sentence. Are you saying that 3.5 will have Touchpoint enhancements
that provide the same functionality as the UM install handlers?
Also see: http://www.eclipse.org/newsportal/article.php?id=76463
To the request of the p2 community, a p2 specific mailing list has been
created and is now available at [EMAIL PROTECTED] You can register at
https://dev.eclipse.org/mailman/listinfo/p2-dev
See you there,
PaScaL___
equinox-dev mailing list
Hi,
Equinox Aspects (some time ago also called AOSGi) has been around for
quite a while now. There has been a lot of community feedback and we
have even seen Equinox Aspects performing in real-world projects.
Therefore the Equinox Aspects team thinks that it is time to move one
big step
