Bug 492059 - Move project org.eclipse.jdt.core.tests.binaries to 1.7
Summary: Move project org.eclipse.jdt.core.tests.binaries to 1.7
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-20 03:37 EDT by Jay Arthanareeswaran CLA
Modified: 2022-07-20 20:24 EDT (History)
0 users

See Also:

Attachments
Patch to up the BREE and bundle version (3.00 KB, patch)
2016-04-20 03:39 EDT, Jay Arthanareeswaran CLA 		no flags Details | Diff
View All 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 Jay Arthanareeswaran CLA 2016-04-20 03:37:53 EDT 
The idea is to limit the requirements of too many runtimes in a developer environment. The triggering point was bug 490012, which made me realize we could do away with dependency on 1.4 altogether.

If anyone has reasons not to do this, please let me know.
Comment 1 Jay Arthanareeswaran CLA 2016-04-20 03:39:11 EDT 
Created attachment 261105 [details]
Patch to up the BREE and bundle version
Comment 2 Eclipse Genie CLA 2020-07-08 13:58:52 EDT 
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 3 Eclipse Genie CLA 2022-07-20 20:24:42 EDT 
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.