|Best Practice for Target Platform Maintenance [message #1263108]
||Tue, 04 March 2014 02:39
| Timo Rohrberg
Registered: September 2011
I was thinking and researching already quite a while about a very important question related to the building of large software systems based on the Eclipse Equinox technology: What are the best practices for maintenance of target platforms?
Background: Imagine a large software system being developed and shipped based on the Eclipse Equinox technology and other Eclipse projects. One always needs to set a defined target platform - so far, so good. But how to maintain those target platforms? Should I mirror and archive the used installable units on my own to make sure they still exist in the expected way when the referred Eclipse projects move on but an older version of my software system needs to be maintained? Or should I refer to the official p2 repositories instead?
If mirroring, what's the best approach for it? Downloading and keeping the artifacts under version control referring to directories of contents within my target definitions? Hosting own local p2 repositories within my development team? But then, how to create those p2 repositories? Download them directly, use the Features and Bundles Publisher, or even the Tycho mirror goal?
I would be very interested in your comments and suggestions. How do you guys maintain your target platforms? What are your experiences and are there any best practices you are aware of?
Thanks a lot for your responses...
Powered by FUDForum
. Page generated in 0.02098 seconds