Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363205

Summary:	Enforce that feature and source feature versions match (for the Eclipse project features)
Product:	[Eclipse Project] Equinox	Reporter:	Tobias Oberlies <t-oberlies>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	kim.moir
Version:	3.7.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Tobias Oberlies

2011-11-08 11:57:33 EST

Currently, it is possible to install one version of the Eclipse platform source feature and a different version of the Eclipse platform (binary) feature. (This really happend to us in a product that we built.)

I would prefer that this is prevented by p2. A way to achieve this would be to include the binary feature in the source feature.

Are there any conceptional reasons not to do this? Sure, this would kind of turn the source features into sdk features (cf. bug 165443 comment 2), but is there a use case for getting only sources without binaries?

I certainly would like to have this enhancement implemented, but even more importantly I would like to know the Eclipse release engineers' opinions on this proposal - because this is the way I would generate source features when we come round to implementing this in Tycho (bug 345234).

Comment 1 Kim Moir

2011-11-08 12:05:56 EST

I don't know if this is really a releng bug.  We generate source bundles and features.  Then our SDKs specify to include both the source and binary features.
Perhaps a question for the p2 team.  Moving to their bucket to see if they have any comments.

Comment 2 Tobias Oberlies

2012-01-11 09:51:55 EST

To repeat the question in short: Does anyone want to install a source feature without the corresponding binary feature?

If not, we could change the source features so that their installation automatically leads to the installation of the right version of the corresponding binary feature.

Comment 3 DJ Houghton

2012-01-11 10:24:36 EST

Kim, is it a valid use case to install a source feature without the corresponding binaries?

Also note that at the plug-in level there is a manifest entry which specifies which binary plug-in the bundle provides the source for. (which means the plug-in versions don't need to match)

Comment 4 Kim Moir

2012-01-11 13:19:26 EST

I have never seen a use case where the source features were installed without the corresponding binaries.

Comment 5 Tobias Oberlies

2012-01-12 07:05:41 EST

(In reply to comment #4)
> I have never seen a use case where the source features were installed without
> the corresponding binaries.
Cheers. This is what I wanted to know, just in case we get around to implementing source features in Tycho ;-)  (bug 345234)

Comment 6 Lars Vogel

2019-11-14 03:23:46 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 7 Alexander Kurtakov

2020-01-15 09:07:13 EST

We are not going to work on this one. In case there is strict dependency one should import the binary feature in the source one.