Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 304499 - Hardcoded versions in org.eclipse.mylyn.commons.net bundle
Summary: Hardcoded versions in org.eclipse.mylyn.commons.net bundle
Status: RESOLVED DUPLICATE of bug 286609
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-03 07:08 EST by Alexander Kurtakov CLA
Modified: 2010-07-09 00:18 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kurtakov CLA 2010-03-03 07:08:33 EST 
All required bundles are required with hardcoded version. If we take for example:
 org.apache.commons.lang;bundle-version="2.3.0" why can't it be  org.apache.commons.lang;bundle-version="[2.3.0,3.0.0)"? Apache commons are really strict about their API so such change should not break anything but it will make life for downstream distributions that are already shipping commons-lang 2.4 for some reason to not have to patch mylyn.
Additionally all apache bundles are reexported. Is it really needed?
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=248986#c45 for details why this shouldn't be done.
Comment 1 Steffen Pingel CLA 2010-07-09 00:18:18 EDT 
I believe the o.e.m.commons.net plug-in just specifies lower bounds for the dependencies, i.e. bundle-version="2.3.0" means 2.3.0 or any later version. Features do include specific versions of the corresponding Orbit bundles though.

The re-export of package is legacy from older Mylyn releases but we can't change this for 3.x stream for backwards compatibility reasons (see bug 286609).

*** This bug has been marked as a duplicate of bug 286609 ***