| Export Product Wizard Problems - No repository found [message #872208] |
Tue, 15 May 2012 17:05  |
 Brandon Lewis
Messages: 268
Registered: May 2012 |
Senior Member |
|
|
I have successfully run and built an Eclipse RCP application in a directory and exported the built product to end users.
I have copied all those files to another directory and committed the code into my revision control system. Thus, I have a working backup copy. (thank goodness)
I have re-launched Eclipse in the new workspace with the revision controlled set of files. They are all checked out, so Eclipse can manipulate them at will.
For my given product configuration, I am able to "Launch an Eclipse Application" from the new directory for the product configuration in question.
I cannot, however, get Export Product Wizard to export the product. I get the following error:
An error occurred while collecting items to be installed
session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: binary,My_Product_root.win32.win32.x86,1.0.0
Unnervingly, in the original directory, I can still export the product just fine.
I have:
1) relaunched Eclipse several times
2) relaunched Eclipse with -clean option
3) cleaned my Project
4) manually removed .metadata from the new workspace and
5) re imported existing projects
I have tracked down that during the Export Product phase, Eclipse itself creates the "missing" bin file in one of its metadata directories:
./.metadata/.plugins/org.eclipse.pde.core/tempp2metadata/binary/My_Product_root.win32.win32.x86_1.0.0
I can remove and watch Export product wizard recreate that file at will.
I can't figure out why the Export wizard can create the file it needs and then not find it. It drives me insane that I can see it, Eclipse can create it, but Eclipse then complains it can't find it.
At my wits ends.
This build process seems to consistently be the most voodoo step of the Eclipse environment for me. I'm not going anywhere near Ant or headless for the time being seeing I can't wrap my head around the basics.
I have searched Google all morning, and almost all mentions of this error point to past upgrades people had moving from Helios to Indigo. I don't have that problem.
Does anyone have any suggestions of steps I've missed, or suggestions of other things I can try?
I may attempt a new product configuration, but that defeats the purpose of checking in the existing product configuration to begin with.
First post.... 
[Updated on: Tue, 15 May 2012 17:19] Report message to a moderator |
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09090 seconds
] 
Search
Help
Register
Login
Home
