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

Bug 351205

Summary:	PDE.Build ignores bundle version from feature.xml
Product:	[Eclipse Project] PDE	Reporter:	Rüdiger Herrmann <ruediger.herrmann>
Component:	Build	Assignee:	pde-build-inbox <pde-build-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	ruediger.herrmann
Version:	3.6.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Rüdiger Herrmann

2011-07-05 11:23:43 EDT

In a feature-based headless build, we have a feature.xml that references a bundle with a specific version like so
  <plugin id="javax.servlet" version="2.5.0.v201103241727" />
The base platform we use to build against (build property 'baseLocation') contains the mentioned bundle twice but with different major versions: 2.5.0.v201103241727 and 3.0.0.x
Despite the explicit version number in the feature.xml, the build output references the 3.0 version of javax.servlet. We would have expected that the resulting feature.xml references the version that we specified (2.5.0.xxx).

We also tried to specify version="2.5.0.qualifier" in the feature.xml - same output. Are we missing something?

Comment 1 Lars Vogel

2018-12-03 09:10:43 EST

Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.

Comment 2 Lars Vogel

2018-12-03 09:13:35 EST

Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.

Comment 3 Eclipse Genie

2020-11-23 00:48:37 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.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2022-11-14 11:41:31 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.

--
The automated Eclipse Genie.