Rowan,
I have good news for you: I have it running by just changing your
config.ini. You have to start the weaving service before the demo
bundle. Otherwise weaving will occour after the Activaor has run.
Please find the modified config.ini attached.
The real problem is, that there is no
As you mentioned earlier, the /p2 directory is not created by the installer
in the installation directory.
I also noticed that the /p2 directory is created and updated [when the
eclipse is running] in the install directory (the directory where the
installer was).
I think that the installer forget
On Wed, 2008-06-11 at 06:57 -0700, Pedro Carneiro wrote:
As you mentioned earlier, the /p2 directory is not created by the installer
in the installation directory.
I also noticed that the /p2 directory is created and updated [when the
eclipse is running] in the install directory (the
As discussed in the planning call this morning our feature names are all
over the map. Here is a sample of some I see in the current testUpdates
repo
Eclipse Project Equinox bundle feature
Eclipse P2 Developer Resources
Equinox bundle source feature
Equinox Provisioning Director
I'm trying to understand how to use the
org.eclipse.equinox.p2.metadata.repository.metadataRepositories
extension point in order to register a factory for my new
IMetadataRepositoryFactory. From what I can see the current
implementation relies on a 'filter' called 'suffix' but I'm unable to
I opened bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=236663 to track.
I can take the Equinox Bundles feature and its source feature. Can someone
on the p2 team take a look at updating the p2 names?
Tom
I will just point out these feature names don't appear anywhere outside
our test updates repository apart from Equinox Provisioning Platform.
The director and generator features are build-time only features that
probably shouldn't even be put on the test update site. They only exist
because of
Torkild/Pedro: I suggest entering bug reports to track these two issues.
I'm not aware of existing bug reports about it.
John
Torkild Ulvøy Resheim [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
06/11/2008 10:13 AM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
Note that there are command line options to the director for both the p2
data area and whether or not to install features.
See the help:
Platform Plug-in Developer Guide - Programmer's Guide -? Packaging and
delivering Eclipse based products - Provisioning platform (p2) -
Installing software
David, it looks like you have correctly surmised the level of support in
p2 for install handlers. P2 cannot install features that use install
handlers because it cannot precisely produce the same runtime environment
under which install handlers ran in Update Manager. Our solution for 3.4
is to
Agreed with Tom on the bundles features.
As for the p2 features, if we are going to change them and it is low risk, why
not change them now. In the precise usecase of Eclipse and the SDK the
features do not show up to the user but they may in other cases no?
For p2 vs Provisioning, I
11 matches
Mail list logo
