Many students prefer to work at home than in the UW CSE instructional labs. But the nice thing about a UW CSE machine is that it already has all of the necessary software for CSE331 installed and is properly configured whereas your computer at home probably is not. We strongly suggest using the CSE lab machines (such as attu), and we will provide support if you have problems with your account. Failing that, you can use the CSE-provided instructional home VM, which nearly replicates the attu environment, and we will also provide support if you have problems with an un-customized home VM. If you wish to set up your own machine to permit you to do your CSE 331 work directly rather than in a virtual machine, this document tells you how to do so. However, the CSE331 staff will not provide support (beyond these instructions) for setting up the CSE331 tools on your own machine; if you have trouble, you are on your own.
Note that even if you choose to work at home, you will still need to complete the Initial Setup on attu.
You want to download Sun's J2SE v6.0 JDK from their web site. This is somewhat tricky because there are a lot of things on the download page with nearly the same name. For example, the JRE is the Java Runtime Environment which lets you run Java programs, but does not provide the tools for Java development.
Thus, go to http://java.sun.com/javase/downloads/index.jsp and make sure that you follow the link labeled Download JDK.
Create an environment variable called JAVA_HOME that points to the directory in which you installed the JDK. To get javadoc to work correctly, you also need to add the bin directory of JAVA_HOME to your PATH environment variable.
To set environment variables on Windows, select System from Control Panel, go to the Advanced tab and hit the Environment Variables button. Add a new variable to the System variables called JAVA_HOME. Its value will be the location of the SDK (which is most likely C:\Program Files\Java\jdk1.6.0_18). Then append %JAVA_HOME%\bin to your PATH environment variable under System variables. This will put the executables associated with the JDK in your path. On Windows, PATH elements are separated by semicolons, so you may have to add a semicolon to the end of your PATH variable before appending %JAVA_HOME%\bin.
To set environment variables in bash, add the following lines to your .bashrc file:
export JAVA_HOME wherever you installed the JDK export PATH=$PATH:$JAVA_HOME/bin
In CSE331, we will use version 3.6 (Helios) of Eclipse.
Eclipse does not come with an installer, so this confuses many people. Basically, you download it, unzip it into a directory, and then run the executable in that directory to start Eclipse. There are some small bugs in Ant within Eclipse that manifest themselves if it is installed in a directory with spaces in its name, so instead of installing it into a directory such as:
C:\Documents and Settings\Joe User\Desktop\eclipse
If you are using a Windows, setup your Eclipse workspace to use the JDK as described in the Tools: Editing, Compiling, Running, and Testing Java Programs handout.
In CSE331 we use the Subclipse SVN Plugin for Eclipse to manage the problem sets. Follow the official installation instructions here to install the Subclipse SVN Eclipse plugin.
When the first problem set has been released, you can check out the cse331 project from your SVN repository by following the checkout instructions for Windows.
The command line should function the same as in the Allen Center software labs, with the exception that when you checkout, you must specify the repository URL as svn+ssh://attu.cs.washington.edu/projects/instr/11wi/cse331/YourUserName/REPOS. For example, to checkout the cse331 directory you should run:
svn checkout svn+ssh://YourUserName@attu.cs.washington.edu/projects/instr/11wi/cse331/YourUserName/REPOS/cse331 cse331
Once you are done with a problem set, you must commit it to SVN, because we collect the problem set by retrieving whatever is in your SVN repository at the deadline. (However, it is recommended to commit frequently, not just when you have completed the problem set.) Also, it is highly recommended to validate the problem set on attu.
attu is the name of an Instructional Workstation (IWS) Linux machine. You will occasionally need to log into this machine.
Use the same password you use to login to the Linux machines in the Allen Center software labs.
If you are using the Linux machines in an Allen Center software lab, you can alternatively use a shorter version of the command:
This works because the username defaults to the username you are currently logged in with and the target domain defaults to the domain of the machine you are connecting from.
However, you should not need to log into attu from an Allen Center Linux IWS machine! Such a machine already has access to the file system based on your CSE account, and attu will be no different.
In either case, your username is your CSENetID, and your password is the same one you use to login to the Linux machines in the Allen Center software labs.
The first time you connecting to attu from a given machine, you will receive a server authenticity warning like this:
The authenticity of host 'attu.cs.washington.edu (188.8.131.52)' can't be established.
Along with the warning, the SSH client will display the RSA key fingerprint of the remote host so that you can verify the host's identity (verifying helps to prevent man-in-the-middle attacks). In our case, it is safe to say 'yes' to continue connecting. When you connect, SSH will cache the host key in order to automatically verify the remote host's identity in the future.
A good article about SSH host keys can be found at http://www.symantec.com/connect/articles/ssh-host-key-protection.
All code that you turn in must run on attu using the staff-supported version of Java. You are permitted to use any version of Java to develop your code (generally speaking, any version of Java 6 will work well), but the CSE331 staff provides technical support only for the staff-supported version, and resolving any discrepancies between Java versions is your own responsibility.
You may use whatever tools you like to develop your code. The CSE331 staff provides technical support only for using Eclipse at UW CSE. This is not because we think that this setup is the only way (or even the best way) to develop Java code, but because we cannot be expected to be familiar with every operating system or text editor that you might choose to use.
If you choose to use Eclipse on your own machine instead of on a UW CSE workstation, and you have problems, then you are generally on your own (The CSE331 staff will try to help you, but only if you are running either Linux or Windows XP, and we make no guarantees.) That being said, it is generally safe to expect Eclipse to behave the same way on all operating systems on which it is supported (which currently includes: Windows 98 and later, Mac OSX, Linux, Solaris 8, AIX, and HP-UX). We know that the UW CSE workstations are not the most powerful machines in existence, so you may find that Eclipse works better when you run it from your own computer.
Back to the
CSE331 home page.
For problems or questions regarding this page, contact: email@example.com.