P2 transport initialization error [message #133966] |
Thu, 02 July 2009 05:36 |
Jeff Norris Messages: 11 Registered: July 2009 |
Junior Member |
|
|
Hi everyone,
I'm adapting the "prestartupdate" example to put together a self-updating
feature-and-product-based P2-enabled RCP application. If I can actually
get this working I'll be happy to share it -- I've seen posts from several
people having trouble pulling this off.
I've met and dealt with dozens of issues already, but this one has me
stumped. I think I'm at the end of the collect phase. I've already
detected that my test product, feature, and plugin need to be updated and
have created the necessary change requests. P2's solver has given its ok
and I'm executing the plan when I get this problem:
Status ERROR: org.eclipse.equinox.p2.engine code=4 An error occurred while
collecting items to be installed null children=[Status ERROR:
org.eclipse.equinox.p2.engine code=0 session context
was:(profile=SDKProfile,
phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
operand=, action=). null Status ERROR: org.eclipse.equinox.p2.repository
code=1002 Unable to read repository at
file:/Users/jnorris/Desktop/TestP2-deploy/repository/plugins /TestP2_1.0.17.jar.
org.eclipse.core.runtime.CoreException: Transport initialization error.
Status ERROR: org.eclipse.equinox.p2.repository code=1002 Unable to read
repository at
file:/Users/jnorris/Desktop/TestP2-deploy/repository/binary/ TestP2-product_root.carbon.macosx.x86_1.0.17.
org.eclipse.core.runtime.CoreException: Transport initialization error.
Status ERROR: org.eclipse.equinox.p2.repository code=1002 Unable to read
repository at
file:/Users/jnorris/Desktop/TestP2-deploy/repository/feature s/TestP2_Feature_1.0.17.jar.
org.eclipse.core.runtime.CoreException: Transport initialization error.]
I'm using file:// URLs for testing but it doesn't seem like that should be
a problem. I've set my artifact and metadata repositories using p2.inf
files that look like this:
instructions.configure=\
addRepository(type:0,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);\
addRepository(type:1,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);
... and as I mentioned, P2 is successfully detecting the changes relative
to that repository.
Any suggestions for me?
Thanks,
Jeff
|
|
|
Re: P2 transport initialization error [message #134103 is a reply to message #133966] |
Fri, 03 July 2009 01:13 |
Jeff Norris Messages: 11 Registered: July 2009 |
Junior Member |
|
|
Ian Bull suggested that this problem could be caused by not having all of
the necessary p2 bundles in the product. He gave me a list (which
basically consisted of every non-source p2 bundle in 3.5) and when I
included all of them this error went away.
So this issue is resolved for me, but I do think it would be a good idea
if this error message was a little less cryptic. I would never have
guessed what the issue was without Ian's suggestion (thanks!)
Jeff
Jeff Norris wrote:
> Hi everyone,
> I'm adapting the "prestartupdate" example to put together a self-updating
> feature-and-product-based P2-enabled RCP application. If I can actually
> get this working I'll be happy to share it -- I've seen posts from several
> people having trouble pulling this off.
> I've met and dealt with dozens of issues already, but this one has me
> stumped. I think I'm at the end of the collect phase. I've already
> detected that my test product, feature, and plugin need to be updated and
> have created the necessary change requests. P2's solver has given its ok
> and I'm executing the plan when I get this problem:
> Status ERROR: org.eclipse.equinox.p2.engine code=4 An error occurred while
> collecting items to be installed null children=[Status ERROR:
> org.eclipse.equinox.p2.engine code=0 session context
> was:(profile=SDKProfile,
> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
> operand=, action=). null Status ERROR: org.eclipse.equinox.p2.repository
> code=1002 Unable to read repository at
>
file:/Users/jnorris/Desktop/TestP2-deploy/repository/plugins /TestP2_1.0.17.jar.
> org.eclipse.core.runtime.CoreException: Transport initialization error.
> Status ERROR: org.eclipse.equinox.p2.repository code=1002 Unable to read
> repository at
>
file:/Users/jnorris/Desktop/TestP2-deploy/repository/binary/ TestP2-product_root.carbon.macosx.x86_1.0.17.
> org.eclipse.core.runtime.CoreException: Transport initialization error.
> Status ERROR: org.eclipse.equinox.p2.repository code=1002 Unable to read
> repository at
>
file:/Users/jnorris/Desktop/TestP2-deploy/repository/feature s/TestP2_Feature_1.0.17.jar.
> org.eclipse.core.runtime.CoreException: Transport initialization error.]
> I'm using file:// URLs for testing but it doesn't seem like that should be
> a problem. I've set my artifact and metadata repositories using p2.inf
> files that look like this:
> instructions.configure=
>
addRepository(type:0,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);
>
addRepository(type:1,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);
> ... and as I mentioned, P2 is successfully detecting the changes relative
> to that repository.
> Any suggestions for me?
> Thanks,
> Jeff
|
|
|
Re: P2 transport initialization error [message #134165 is a reply to message #134103] |
Fri, 03 July 2009 08:14 |
Cédric Vidal Messages: 101 Registered: July 2009 |
Senior Member |
|
|
Hi Jeff,
I'm having exactly the same problem. I've tried added all possible p2
bundles I know but it doesn't change anything, I'm having the same error.
Would you mind sharing this us the list of bundles you're using ?
What's more the wierd thing is I'm having this problem both in straight
P2 Installer 3.5 and in a home made custom product. This would mean that
an important bundle has not been bundled with P2 Installer during
packaging.
Regards,
Cédric
Jeff Norris a écrit :
>
> Ian Bull suggested that this problem could be caused by not having all
> of the necessary p2 bundles in the product. He gave me a list (which
> basically consisted of every non-source p2 bundle in 3.5) and when I
> included all of them this error went away.
> So this issue is resolved for me, but I do think it would be a good idea
> if this error message was a little less cryptic. I would never have
> guessed what the issue was without Ian's suggestion (thanks!)
>
> Jeff
>
>
> Jeff Norris wrote:
>
>
>> Hi everyone,
>
>> I'm adapting the "prestartupdate" example to put together a
>> self-updating feature-and-product-based P2-enabled RCP application.
>> If I can actually get this working I'll be happy to share it -- I've
>> seen posts from several people having trouble pulling this off.
>
>> I've met and dealt with dozens of issues already, but this one has me
>> stumped. I think I'm at the end of the collect phase. I've already
>> detected that my test product, feature, and plugin need to be updated
>> and have created the necessary change requests. P2's solver has given
>> its ok and I'm executing the plan when I get this problem:
>
>> Status ERROR: org.eclipse.equinox.p2.engine code=4 An error occurred
>> while collecting items to be installed null children=[Status ERROR:
>> org.eclipse.equinox.p2.engine code=0 session context
>> was:(profile=SDKProfile,
>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>> operand=, action=). null Status ERROR:
>> org.eclipse.equinox.p2.repository code=1002 Unable to read repository at
> file:/Users/jnorris/Desktop/TestP2-deploy/repository/plugins /TestP2_1.0.17.jar.
>
>> org.eclipse.core.runtime.CoreException: Transport initialization
>> error. Status ERROR: org.eclipse.equinox.p2.repository code=1002
>> Unable to read repository at
> file:/Users/jnorris/Desktop/TestP2-deploy/repository/binary/ TestP2-product_root.carbon.macosx.x86_1.0.17.
>
>> org.eclipse.core.runtime.CoreException: Transport initialization
>> error. Status ERROR: org.eclipse.equinox.p2.repository code=1002
>> Unable to read repository at
> file:/Users/jnorris/Desktop/TestP2-deploy/repository/feature s/TestP2_Feature_1.0.17.jar.
>
>> org.eclipse.core.runtime.CoreException: Transport initialization error.]
>
>> I'm using file:// URLs for testing but it doesn't seem like that
>> should be a problem. I've set my artifact and metadata repositories
>> using p2.inf files that look like this:
>
>> instructions.configure=
>
>>
> addRepository(type:0,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);
>
>
>>
> addRepository(type:1,location:file${#58}///Users/jnorris/Sit es/TestP2-deploy/repository);
>
>
>> ... and as I mentioned, P2 is successfully detecting the changes
>> relative to that repository.
>
>> Any suggestions for me?
>
>> Thanks,
>> Jeff
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03894 seconds