Bug 155678 - Eclipse 3.2 don't save JUNIT_HOME/JUNIT_SRC_HOME
Summary: Eclipse 3.2 don't save JUNIT_HOME/JUNIT_SRC_HOME
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M5   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 156226
Blocks:
  Show dependency tree
 
Reported: 2006-08-30 08:41 EDT by Marcus Walla CLA
Modified: 2007-02-07 12:12 EST (History)
2 users (show)

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 Marcus Walla CLA 2006-08-30 08:41:23 EDT 
I hope I selected the right component. 

Before I tell you the bug I have to mention that I used Eclipse 3.1 before.
I have the problem that Eclipse don't seem to save the information after I have changed the JUNIT_HOME (and the JUNIT_SRC_HOME) variable to the new JUnit installation of JUnit 4.1. I changed this setting 
by clicking on the project with the right mouse button (in the package explorer view), selecting "Build Path->Configure Build Path...", clicking on the JUNIT_HOME variable and told Eclipse to "Edit..." it. After that I changed the "Variable..." and "Extension..." and leaved all dialog boxes with the "OK" button. Until I finish Eclipse this works fine. But the next time I started Eclipse again the variable are set to the old version with the wrong jar file, so that I have to make the above changes again. The combination of the folder and the including jar file is wrong!
Comment 1 Stefan Langer CLA 2006-08-30 09:04:59 EDT 
I had the same problem and resolved it by adding a custom variable called JUNIT4_HOME. I also was using 3.1 with JUNIT3.8 prior to upgrading to Eclipse 3.2.
Comment 2 Martin Aeschlimann CLA 2006-09-05 12:59:25 EDT 
It is a known problem with classpath variables that they allow to be edited but are overwritten on startup again. Bug 156226 is for that.

In 3.2 JUNIT_HOME got replaced by the JUnit container: Remove you classpath entry and add Library > JUnit where you can configure 3.8.1 or 4.1

*** This bug has been marked as a duplicate of 156226 ***
Comment 3 Frederic Fusier CLA 2007-01-19 12:18:14 EST 
Reopen to set correct duplicate bug...
Comment 4 Frederic Fusier CLA 2007-01-19 12:23:00 EST 
In fact this bug is not a duplicate of bug 156226 but depends on it. Now that bug is fixed, UI may change to warn user that this variable cannot be changed...
Comment 5 Markus Keller CLA 2007-02-07 04:10:41 EST 
JUNIT_HOME and UNIT_SRC_HOME have been marked as deprecated and read-only,
Comment 6 Dani Megert CLA 2007-02-07 12:12:03 EST 
Verified in I20070207-0800.