| - P2 - No action found for: org.eclipse.equinox.p2.touchpoint.eclipse.addRepository. [message #504292] |
Fri, 18 December 2009 00:53  |
Eclipse User |
|
|
|
Hello everyone,
I am sorry to post this one again. I already posted it in the p2 dev - Forum but it seems nothing happens there. And it seems question depending p2 are answered in this forum.
We have a working update site for a rcp-product and we use eclipse3.4. I created the product with the org.eclipse.equinox.p2.director.
Now we want to upgrade to 3.5 and there starts the problem. If I use the same configuration with the change of some depending plugins I can create a running rcp product but I cannot add repositories to the available software site page because the add button is missing. Then I read of the possibility to use the p2.inf file. Now the rcp product shows the update site.
If I want to upgrade the rcp-product directly from the update site, because that is what I have to do with around 30 installations, the upgrade first seems to work. But then after everything is downloaded I get the following error while configuring the rcp-product bundle:
An error occurred while configuring the installed items
java.lang.IllegalArgumentException: No action found for: org.eclipse.equinox.p2.touchpoint.eclipse.addRepository.
at org.eclipse.equinox.internal.p2.engine.InstructionParser.loo kupAction(InstructionParser.java:66)
at org.eclipse.equinox.internal.p2.engine.InstructionParser.par seAction(InstructionParser.java:44)
at org.eclipse.equinox.internal.p2.engine.InstructionParser.par seActions(InstructionParser.java:34)
at org.eclipse.equinox.internal.provisional.p2.engine.Installab leUnitPhase.getActions(InstallableUnitPhase.java:161)
at org.eclipse.equinox.internal.provisional.p2.engine.phases.Co nfigure.getActions(Configure.java:34)
at org.eclipse.equinox.internal.provisional.p2.engine.Installab leUnitPhase.getActions(InstallableUnitPhase.java:117)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mai nPerform(Phase.java:111)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.per form(Phase.java:79)
at org.eclipse.equinox.internal.provisional.p2.engine.Installab leUnitPhase.perform(InstallableUnitPhase.java:53)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.per form(Phase.java:46)
at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet. perform(PhaseSet.java:38)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.pe rform(Engine.java:53)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.Pr ovisioningUtil.performProvisioningPlan(ProvisioningUtil.java :265)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.Pr ofileModificationOperation.doExecute(ProfileModificationOper ation.java:58)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.Pr ovisioningOperation.execute(ProvisioningOperation.java:40)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningO perationRunner$1.run(ProvisioningOperationRunner.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
In all other posts there is the hint to use the fully qualified name. But that is what I am doing.
Is there a problem because the addRepository-action didn't exist under 3.4? But I thought this should not make any problem configuring the new product depending on 3.5.
If I upgrade the 3.4-version to 3.5 without the p2.inf it works, but all Update-site setting are lost and cannot be added directly because of the missing add button.
I hope you understand my problem and can help me.
Hauke
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03940 seconds
Home