[news.eclipse.technology.equinox] Re: [P2] Updates treated as conflicts

[Laurent Marchal <lmarchal@xxxxxxxxxx>]

Ok I found the solution :
I tried all the possibilities to find what was wrong : install with the 
p2 agent, use the p2 installer, tried the p2 mirrorring... Everything 
was working so the problem did not come from my "update site" repository.

The error in my RCP app was : "No repository found containing: some 
bundles" which means no ARTIFACT repository found containing the 
bundles. My p2.inf was like :

addRepository(type:0,enabled:true,name:Updates,location:http${#58}//some.update.site);

After reading for the 10th time the documentation 
http://wiki.eclipse.org/Equinox_p2_Touchpoint_Instructions I saw that 
the "type" parameter indicates if it's a metadata repository or an 
artifact repository. OK! I have only declared the metadata repository 
not the artifact one in the p2.inf, so the artifact repository could 
never be found !

Now the valid p2.inf is like :

addRepository(type:0,enabled:true,name:Updates,location:http${#58}//some.update.site);
addRepository(type:1,enabled:true,name:Updates,location:http${#58}//some.update.site);

and everything is working nicely !

Thanks everyone for your help.
Hope with time that p2 will be become simple for simple things.

Laurent Marchal.

Christian a écrit :
> Laurent Marchal schrieb:
> > I can install the RCP application directly from my update site using 
> > the p2 agent without any problems. It's just the update that is not 
> > working, I'm stuck with "No repository found" for all the bundles...
> >
> > Laurent.
>
> Do you have that magical p2.inf  file next to your product when exporting?