From: SourceForge.net <no...@so...> - 2009-12-01 02:20:34
|
Feature Requests item #1526798, was opened at 2006-07-22 01:10 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=365278&aid=1526798&group_id=15278 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: David Saff (dsaff) Summary: JUnit .jar should work in jre\lib\ext Initial Comment: It would be very nice if the junit-4.1.jar could just be dropped into <java dir>\jre\lib\ext without having to always declare a CLASSPATH. The following two changes have been verified to work on Windows 2000: 1. On line 70 of org\junit\runner\JUnitCore.java, replace the text "Class.forName(each)" with the text "Class.forName(each, true, ClassLoader.getSystemClassLoader())". 2. On line 209 of junit\runner\BaseTestRunner.java, replace the text "Class.forName(suiteClassName)" with the text "Class.forName(suiteClassName, true, ClassLoader.getSystemClassLoader())". With these two changes made, the standard suite of tests (the "AllTests" suite) passes (on a Windows 2000 system using JDK 1.5.0_07) with "junit-4.1.jar" dropped into the "...\jre\lib\ext" directory and with the CLASSPATH variable left blank. If there is no subtle reason why these changes shouldn't be made (I am a complete JUnit greenhorn and may not know of some well-known problem), then these changes could make the installation of JUnit much easier for us command-line users. Thank you, Eric R. Salberta eri...@L-... ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-12-01 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2009-11-16 17:52 Message: This tracker is being shut down. Please move this item to http://github.com/KentBeck/junit/issues ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2006-09-29 13:31 Message: Logged In: YES user_id=325156 Actually, I'm pretty sure that simply making those changes would break the Eclipse JUnit Plug-in test loader, among other possible things. I'll modify this feature request to include: 1) A command-line switch that enables the system class loader 2) Tests for both behaviors. ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2006-09-29 13:27 Message: Logged In: YES user_id=325156 I'm referring to the mailing list for comment--I think some people use custom classloaders, and this might screw them up (I haven't thought deeply enough to know exactly how). I'll come back to this in a week. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=365278&aid=1526798&group_id=15278 |