Bug 118673 – Duplicate JRE_LIB classpath entry for java projects

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 118673 - Duplicate JRE_LIB classpath entry for java projects

Summary:	Duplicate JRE_LIB classpath entry for java projects

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Developer Suite
Classification:	Retired
Component:	JDT (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	ia64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ben Konrath
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-03-18 14:50 EST by Jeremy Handcock
Modified:	2007-04-18 13:04 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-12-01 09:52:07 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Jeremy Handcock 2004-03-18 14:50:38 EST

Description of problem: There is a duplicate classpath entry
/opt/bea/jrockit-j2sdk1.4.2_03/jre/lib/managementapi.jar in new java
projects created when running under the JRockit JVM on ia64.  Eclipse
doesn't like this and won't allow you to create a new java project or
build a pre-existing one.

How reproducible: Always


Steps to Reproduce:
1. Create a new java project
2. Look at the project's build path - two managementapi.jar files!

We'll consider this when deciding what JVM to use on ia64.

Comment 1 Andrew Overholt 2004-11-29 10:28:38 EST

Ben, can you comment on this?  I think it should probably be closed. 
Reassigning to bkonrath in the mean time.

Comment 2 Ben Konrath 2004-12-01 09:52:07 EST

This bug isn't present in RHDS 2.0 (eclispe 3.0), closing bug.

Note You need to log in before you can comment on or make changes to this bug.