The Creation of a Razor Java Development Environment

The Problem (1) n n Java developers require a common area containing ‘ready’ classes.

The Problem (2) n n n JDK 1. 2 is required by SPS 2001

The Solution (1) n n n A development configuration area (DCA) will be created

The Solution (2) n n The host machine for the DCA and compilation will

The Process n n n User checks some. java files into Razor and marks

The System Host of repository Developer’s PC Windows repsrv Host of pcrops account inc.

The System Developer’s PC Host of repository Razor client checks-out/in source repsrv pcrsrv 1

Remaining Issues (1) n n n We need to decide upon a ‘standard’ JDK

Remaining Issues (2) The options as we see it at the moment are: –

Slides: 10

Download presentation

The Creation of a Razor / Java Development Environment Stephen Page Razor

The Problem (1) n n Java developers require a common area containing ‘ready’ classes. It is not desirable for each developer to have a personal copy of all class files. Developers must be able to create new development versions of classes which can be compiled with classes in the common area.

The Problem (2) n n n JDK 1. 2 is required by SPS 2001 - there is currently no version 1. 2 of the JDK for HP-UX. Windows and Linux are the alternative platforms. Java development is multi-platform - Windows must be supported as well as Unix. Java compilations depend upon a CLASSPATH environment variable, which must be set.

The Solution (1) n n n A development configuration area (DCA) will be created for each Razor group. Files marked as ‘ready’ in Razor will be automatically checked-out read-only to the DCA. Developers will use their development CLASSPATH to compile with new versions of files in their accounts before those in the DCA.

The Solution (2) n n The host machine for the DCA and compilation will be a Linux PC for availability of JDK 1. 2. Windows access to the DCA will be provided by the ‘Samba’ file sharing system running on the Linux PC. This is transparent to the user.

The Process n n n User checks some. java files into Razor and marks them as ‘ready’. Razor checks-out the files read-only to the DCA. ----------Compilation is started----------Razor opens a remote shell from repsrv to the Linux PC. A script provided by me sources the pcrops. login then checks for the existence of a ‘make script’ provided by the developers in the DCA. If one is found, then it is run. The ‘make script’ sets the CLASSPATH and then compiles the. java files.

The System Host of repository Developer’s PC Windows repsrv Host of pcrops account inc. DCA pcrsrv 1 Compilation and SMB re-export of DCA Linux PC

The System Developer’s PC Host of repository Razor client checks-out/in source repsrv pcrsrv 1 Windows Razor auto-runs check-out r/o of source & runs Host of pcrops account inc. DCA compilation script Compiled output installed in DCA NFS: Share DCA (/user/pcrops/dca) Developer creates / modifies source Samba: Share DCA Compilation and SMB re-export of DCA Linux PC

Remaining Issues (1) n n n We need to decide upon a ‘standard’ JDK version. Different people are using different versions, not all of them from Sun. Razor only allows us to set actions on a per file basis. Compilation must only be started after the last file is checked-in so that dependencies are satisfied. Compilation of the files in the DCA must therefore be triggered somehow.

Remaining Issues (2) The options as we see it at the moment are: – User command which starts the compilation. This may be added to the Razor GUI. This could also allow compilation of a selected subset of the DCA rather than the entire area. – A cron job which runs compilations at set frequencies.