[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] update site from the product build

This should work exactly as you describe it (I assume your bundles also have monotonically increasing version numbers). 

If you crack open the content.xml do you see your updated IUs (that is, the metadata corresponding to the new products / features / bundles you built)?  I wonder if you are pointing to an old version of the repository.

cheers,
ian

On Fri, Oct 2, 2009 at 9:23 AM, Andy Jin <AJin@xxxxxxx> wrote:

I have a product build using P2 with “p2.gathering” on. The product contains of one master feature which contains all the other sub-features. The master feature also contains the Eclipse platform (which contains all the P2 bundles).

 

The product build generates a “buildRepo” directory. In that directory there are “binary”, “feature” and “plugins” folder, and “content.xml” and “artifacts.xml” file.

 

We have daily builds. Each build increase the build qualifier in the product ID (e.g. 1.0.0.20090930 to 1.0.0.20091001). The main features and sub-features also has build qualifier increased daily.

 

I run build 1.0.0.20090930 and add a new update site URL pointing to the “buildRepo” from build 1.0.0.20091001. However when I run “Check for update” I get “There is nothing to update” message.

 

Is there anything wrong with my config? Can I use the “buildRepo” directly as update site?

 

Thanks,

Andy


_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev




--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource