p2

I'm adding an update feature in my Eclipse E4 application. Herefor I used the source code and tutorial from Lars Vogel. When I test my application the provisioningJob is always null. It should only be null when it run into Eclipse. But when I try to update my exported application the provisioningJob is still null. What I'm doing wrong? public class UpdateHandler { private static final String REPOSITORY_LOC = System.getProperty("UpdateHandler.Repo", "file:////updateServer/repository"); @Execute public void execute(final IProvisioningAgent agent, final Shell shell, final UISynchronize sync,

When building a product based on Eclipse 3.7+, I want to include a marketplace feature (org.eclipse.epp.mpc). I don't want to explicitly add this feature to one of the product features because I am also building for Eclipse 3.5. Is there a way to add this feature during the build? It is currently not possible to create a product distribution which contains additional features, i.e. features which are not directly or indirectly referenced from the product. This enhancement was requested in this ticket , but is not available in the current Tycho version (0.16.0). However there is the possibility

I'm building an Eclipse Feature that has a requirement that amounts to this... The Feature must be able to be uninstalled automatically if the user has his license revoked. If you want more background information about that, Here is another question that I've asked on this topic. Thanks to the answers on that question, I've been trying to learn the Eclipse p2 director api. I've found some classes that look useful here I've been trying to instantiate one of these classes in my code, but with no luck yet. I've been reading the help documentation, and I'm getting kind of lost in it all. I'm stuck

I'm using Eclipse 3.5.2 and I've created a p2.inf with the following information: instructions.install = \ chmod(targetDir:@artifact,targetFile:$os$/libfoo.so,permissions:755); instructions.install.import= \ org.eclipse.equinox.p2.touchpoint.natives.chmod I placed the p2.inf inside the META-INF folder of the fragment, but when I install the update site, libfoo.so does not have execute permissions. After pulling my hair out, I tried a p2.inf referencing a non-existing *.so, but nothing seems to happen. No error messages, exceptions, or warnings of any kind to indicate the P2 touchpoint action

There is an article in the Eclipse wiki how to configure user's p2 default repositories of an RCP application by adding a static conf file to your product: Equinox/p2/Adding Self-Update to an RCP Application - Configuring the user's default repositories I want to do the same programmatically in a Java class when the user changes some configuration details. I could not find appropriate p2 API documentation for that. Use this solution for Eclipse 3.7 based applications: final ProvisioningUI ui = ProvUIActivator.getDefault().getProvisioningUI(); IArtifactRepositoryManager artifactManager = ProvUI

In my Eclipse project, I defined a simple plugin (bundle), a feature that includes the plugin and a product that includes the feature. When I export the poduct (via the "Eclipse Product export wizard" of the product editor), it does build the product. I can launch the product, everything works fine (the plugin is there and doing what it is supposed to do). The only problem is that the user of the product cannot install additional Eclipse features using the Software Update menu (Help -> Software Updates). The Software Updates sub-menus ("Find and Install..." and "Manage Configuration...") are

I know I can set start levels and auto-start flags for bundles in Eclipse using a p2.inf file or using a product definition file. Doing it in the product file gives me tooling support and puts the settings into my launch configuration. On the other hand, using the p2.inf file allows me to manage start levels on a per-feature basis which give me a nice grouping of start-level settings. Now my questions: What's the preferred way of defining start-levels and auto-start flags? p2.inf seems a bit outdated but is there a way to define start-levels and auto-start flags on a per-feature basis without

I considered using SBT (which resolves dependencies using Ivy) to build an Eclipse RCP application. Is it possible? If you can access the p2 repository via the standard ivy resolvers(listed here: http://ant.apache.org/ivy/history/latest-milestone/settings/resolvers.html ) then it should be possible. 来源： https://stackoverflow.com/questions/6256963/can-apache-ivy-handle-dependencies-in-p2-repositories