|I looked at your scripts and saw that you manually write down the XML for the composite repository. That's ok, but if I remember correctly, XML serialization is not API for p2, it can change anytime (. I like better calling p2 directly. |
Unfortunately the p2-agent standalone RCP product is not build anymore with the platform. So I took the .product still lying in the p2 source repository and updated it to work with Kepler.
I also added a new application for creating composite repository as currently in p2 there is only an Ant tasks to do that. The result is a light (< 10MB) standalone RCP application with all p2 applications and the new composite one.
Hope this helps.
I find it cumbersome and error-prone that I have to look up the latest Orbit build on http://download.eclipse.org/tools/orbit/downloads modify my various build scripts accordingly before I can kick a build. So I've created a cron job that updates the following p2 composite repos in 5 minute intervals:
http://download.eclipse.org/modeling/emf/cdo/orbit/latest-I (currently empty)
http://download.eclipse.org/modeling/emf/cdo/orbit/latest-M (currently empty)
Each composite contains at most one child repo which is the latest Orbit repo of the respective build type, i.e., R, S, I or M-build. The p2.timestamp of a composite only changes when the child location changes.
Please feel free to use these stable URLs yourself if you find them handy ;-)
P.S.: I'm not a bash expert, so I attach the used bash scripts to this post. Please provide feedback if there's something wrong with them.
cross-project-issues-dev mailing list