Sometimes Ant cannot find the JRE to run the JUnit tests – this can easily be fixed by right clicking on the build.xml file, selecting “Run As..” -> “External Tools Configuration”. Choose the JRE tab far to the right and select the JRE that the workspace also runs.
Eclipse 3.6.1 Linux General, Junit 4.0 and ant 1.71.2.
When trying to develop unit tests using JUnit 4 and Ant 1.71 in Eclipse 3.6.1, I kept getting this error even though I had added JUnit.jar to the Eclipse buildpath:
The <classpath> for <junit> must include junit.jar if not in Ant's own classpath
The solution was to do the following:
Window -> Preferences -> Ant -> Runtime -> Classpath: Add JUnit.jar to the Global Entries as an external Jar-file.
First of all, determine which Linux Kernel version you are running using the command:
sudo uname -r
Then go to System ->Administration -> “Synaptic Package Manager”.
Search for “linux-image-“, arrange by installed packages (click at the column header most to the left) and then completely remove all linux kernels (linux-images) that are older than you current version.
Then run the command:
Enable the partner repository in order to download Sun Java6 JDK: System -> Software Sources -> Other Software -> http://archive.canonical.com/ubuntu partner)
Get the following packages from System -> Synaptic Package Manager:
- sqldeveloper-package (this is a special package that contains all prerequisites except sun-java6-jdk)
Download “Oracle SQL Developer for other platforms” from bottom of Oracles website:
Extract the archive to a folder and make the sqldeveloper.sh file executable (right click on it and select properties->permissions).
Run Oracle SQL Developer for the first time by typing the following command in the console:
When requested for a JVM directory, use something like this:
Click the save all button (this saves the path of the JVM directory) and then close the program.
You can now use the Oracle SQL Developer by running the following command:
I would recommend making a launcher for it – just right click on the desktop. Avoid using “~” in the path.