1 / 10

The Creation of a Razor / Java Development Environment

Razor. The Creation of a Razor / Java Development Environment. Stephen Page. The Problem (1). 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.

calvin
Download Presentation

The Creation of a Razor / Java Development Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. The Problem (1) • 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.

  3. The Problem (2) • JDK 1.2 is required by SPS2001 - 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.

  4. The Solution (1) • 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.

  5. The Solution (2) • 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.

  6. The Process • 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.

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

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

  9. Remaining Issues (1) • 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.

  10. 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.

More Related