Community
Participate
Working Groups
Build Identifier: 3.6.0 I20100608-0911 I have multiple problems with P2 preferences in my Application (based on product build) I have a separate build project (releng). The build creates a local repository in the build project. After the build is successful, the idea here is to copy the repository to our application specific URL. - In my p2.inf file, I have addRepository entries pointing to my application specific URL. I have only 2 lines in my P2.inf, one pointing to artifacts repository and other to metadata repository - In my build script, I have "p2.build.repo" pointing to my local repository - When I run the build all I'm expecting in org.eclipse.equinox.p2.artifact.repository.prefs & org.eclipse.equinox.p2.metadata.repository.prefs is to point to the repository I have specified in my p2.inf But, the preferences inconsistent and has repository information about my local repository, eclipse update site and application final repository. Also these things keep changing for every build, sometimes I see all these entries, sometimes it ignores my local repository and points to the default repository URI provided by the product build. I'm so confused and tired. I also found org.eclipse.pde.build.container.feature/product/p2.inf has inconsistent and varying repository information for each build when the build script is not changed I would like my application to point only to the repository i have specified in P2.inf. How to do this? Reproducible: Always
Also, its caching the old repository information I specified in my P2.inf file. Because it kept using the old repository information. I restarted my eclipse workspace and started the build, now it's not even showing my repository information I have specified in the p2.inf, shows only eclipse update site. I'm confused because, I see my repository information in org.eclipse.pde.build.container.feature/product/p2.inf
I noticed that the previous repository information is cached in ${workspace}\.metadata\.plugins\org.eclipse.search\dialog_settings.xml. Even though I change the repository URL in my P2.inf, its (incl) adding previous repository information found in the cache.
The cache is cleared only on restarting the workspace.
Paul, do you know what might be going on here? This seems strange to me. I think that is the IMemento storage file so I have no idea why there would be repository information stored in a memento in the search bundle.
(In reply to comment #4) > Paul, do you know what might be going on here? This seems strange to me. I > think that is the IMemento storage file so I have no idea why there would be > repository information stored in a memento in the search bundle. The only reason for them to be mentioned in search is that they were searched for. Nothing in p2 will read stuff out of search. If you show us a segment of the file you are concerned about though, we could be sure. In general, there should be prefs under p2/org.eclipse.equinox.p2.engine and p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile in your install that show repos. If you upgrade from build to build, won't they just accumulate? PW
Eclipse prefs under p2/org.eclipse.equinox.p2.engine will have information about the repositories added to Eclipse IDE. But I'm talking about the repositories that I have added to my RCP application. The P2.inf in our application will change based on the environment (dev, QA...), the problem is that even though I change the repo information for each build, Eclipse is using only the initial repositories specified in our P2.inf file. If I restart the workspace, it works fine.
This looks like something that we should investigate for 3.7
No time in 3.7.
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.
