If anyone is interested in tracking this issue until the move to version
of ECF (i.e. the 'optional on org.eclipse.core.net but not really'), see
bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=216478
Scott
Timothy Webb wrote:
Thanks, the optional flag was indeed the trick. Once I asked f
Thanks, the optional flag was indeed the trick. Once I asked for
optional bundles to be included, the add required picked up 3
additional bundles and the launch configuration worked as expected.
Cheers,
Tim
On Jan 30, 2008, at 10:48 AM, DJ Houghton wrote:
We've recently updated ECF to a ne
I expect the problem is that you need to ask the org.eclipse.core.net
plug-in to the launch configuration. The dependency was introduced by the
latest release of ECF.
- Dave
[equinox-dev] [prov] Trick to using repo optimizer?
Tim Webb
to:
Equinox development mailing list
01/30
We've recently updated ECF to a new version and it brings in the core.net
bundle. Try updating your launch config to add this new bundle with the
"add required bundles" button.
(yes, ECF's dependency on core.net is optional but not really yet... this
will be fixed in the next release of ECF)
[EM
Is there a trick to using the repo optimizer for p2 to generate the pack200
files? When I run the optimize OSGi app off of HEAD, I receive the
following error. Validating the bundle hierarchy seems to show no issues.
I've tried running the workspace off of 3.4M4 as well as the latest
integration
