After succeeding in getting Equinox to run with security on, I'm now
experimenting with signed bundles. First I made a new keystore, using
the standard java keytool, like this:
keytool -genkey -alias myalias -keystore keystore
I created a bundle using Eclipse's PDE, and used the Export
The director.app bundle version included in the build was calling old APIs
which didn't exist in the director anymore, so the director was unable to
run and provision anything. This also explains why the nightly builds are
ok but the i-build was busted. (HEAD was ok)
This was due to new code
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
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
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
Are things in churn right now with the metadata generator? It seems
to be producing meta with the wrong touchpoint type. Here's a snippit
from the generated content.xml that I received:
touchpoint id=null version=0.0.0 /
touchpointData size=1
instructions size=2
instruction
This is not really expected. That said earlier today I ran a provisioning
operation using these actions and everything worked fine.
Could you please open a bug about it, thx.
PaScaL
does this affect PDE at all when targetting something installed using
p2? That is, do you still get the source in the IDE ?
Jeff
Pascal Rapicault wrote:
Earlier today I have released support to ensure that the source bundles
would not get added to the bundles.txt (and therefore not installed
PDE is la raison d'etre of this support. When we decided to no longer add
the source bundles to the bundles.txt (a week or so ago), PDE could not
find the source bundles any more since the content of its target is solely
derived from the bundles.txt. Therefore PDE needed an extra place to get
the
