| Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt) |
|
Ah, that's it. Perfect. Thanks Markus!
IMHO, we should make this mandatory for all packages and have someone just go in and do it.
Doug. From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Markus Knauer [mknauer@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 23, 2015 3:44 PM To: Cross project issues Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt) *** Automatically check for updates:
*** Package structure:That's enabled in all packages, and all of them are looking for updates of their root feature(s) once every week. All Mars packages (with the exception of the RCP/RAP package) are using a single root feature that is checked for a higher version. This root feature is an EPP feature and controlled by the package maintainers. In theory it could be updated and the respective package would be updated with the new content. Of course, this works only if the update content is available from one of the p2 repositories built into the packages (which is the Simultaneous Release p2 repository). The RCP/RAP package structure has changed with Mars, as an experiment in order to get some experience and as a way to "convince" others in the Neon timeframe to change the package structure of the remaining packages. In this package *all* content features are installed as root features and therefore checked for updates. Personally I think that's the way to go for all packages. The fact that it is enabled in RCP/RAP gives us a chance to get some experience in order to roll it out for all packages in the Neon timeframe.
Regards,
Markus
On 23 September 2015 at 21:31, Doug Schaefer
<dschaefer@xxxxxxx> wrote:
Step 1 - test to see whether it works. Anecdotal evidence says it doesn't. Something about how the EPP packages are defined and built. Also projects need to make sure the URLs for maintenance p2 sites are correct and enabled by default. |