Community
Participate
Working Groups
Build Identifier: I20100406-1034 Currently it's impossible to install via p2 a standalone bundle. A repository should be built around the bundle and it should added to the list of known repositories before using p2 provinstall command. The process is too heavy and could be significantly shortened if provinstall command creates by itself a temporary repository containing the "standalone" bundle. For test purposes it would be useful if it's possible to install non-signed bundles - for example with option that could switch on/off trust validation. Reproducible: Always Steps to Reproduce: If the bundle is installed via standard install command, it will disappear after restart.
Created attachment 174616 [details] provinstall command enhanced to install standalone bundle provapplychanges command added to console bundle in order to be possible to apply changes runtime (to write newly installed bundle into corresponding bundles.info file) -disableCheckTrust option added to be able to install non-signed bundles
Created attachment 184934 [details] provApplyChangesCommand _provapplychanges command added to apply configuration at runtime. Optional dependency to org.eclipse.equinox.internal.provisional.configurator.Configurator Declarative services and simple configurator bundles should be available and started
Hello ! I successfully applied patch 184934. What is the difference between using this new _provapplychanges and the old confapply available in org.eclipse.equinox.internal.simpleconfigurator.console.ConfiguratorCommandProvider ? It looks like they both call org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration() Thanks
Yes, the implementation is almost the same - the reason to introduce a new command is mainly usability. If the user doesn't know how different p2 components work together, it's very hard to find the Configurator command - that's why it didn't come to my mind when I was reading your mail. But during the discussion with you I started to think that usability aspect could be covered by other means. What do you think would help more: - provinstall documentation which notes that applychanges command should be invoked in order to see your changes at runtime; - applychanges to be implied in provinstall command; - if you have other option to propose? Thanks.
Hello, I think that we could keep the provapplychanges command the same way it is; maybe just documenting the command saying it is (almost) an alias to the confapply command. Thanks !
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
