Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345443 - Investigate how we would consume a p2 binary build
Summary: Investigate how we would consume a p2 binary build
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 11:18 EDT by Pascal Rapicault CLA
Modified: 2020-01-15 09:08 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2011-05-11 11:18:29 EDT
Going forward, p2 would like to have its own build and provide the SDK build with binaries instead of having the SDK build p2 itself. This would allow for p2 to move at a different pace (more frequent builds, different release schedule, etc.) and would also reduce the time of the SDK build.
Comment 1 John Arthorne CLA 2011-05-11 13:05:40 EDT
This shouldn't be too difficult - we do this already for parts of the 4.1 SDK build. Isn't it just a matter of using the p2 fetch factory to fetch binary bundles from a repo rather than source?
Comment 2 Kim Moir CLA 2011-05-11 13:16:18 EDT
Yes.  

We would also have to setup a p2 build to generate the repo that the SDK would consume. This isn't difficult to do.
Comment 3 Lars Vogel CLA 2019-11-14 03:40:07 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.
Comment 4 Alexander Kurtakov CLA 2020-01-15 09:08:01 EST
Plans for separate releng are gone now.