****************************************

 Filename:	README.config  
 Software:	JBuilder 2005 Foundation
 Locker:	jbuilder_v2005
 Last Updated:	12/15/05
		
****************************************

VOLUMES IN LOCKER:	

	sw.jbuilder_v2005 	top-level	replicated	


LINKS TO VOLUMES/LOCKERS:


CHANGES FOR ATHENA:


PROGRAMS IN LOCKER:	jbuilder - main application
			
STARTUP SCRIPT: ours, in ../arch/share/bin/bin directory.

    DESCRIPTION 
	our local script sets up platform-independent user local config files,
        then invokes vendor binary in JBuilder2005/bin.

    INSTALLATION 

Vendor has installers for main application, documentation, examples
and ant ("extras") for each platform. Installers should be unpacked into a
temporary location and run- installation can be done directly into AFS
space. Install path: /mit/jbuilder_v2005/distrib/$ATHENA_SYS/JBuilder2005
(vendor expects top level to be directory JBuilder2005).

An annual license key is no longer required.

On first use, it creates local config directories ~/.jbuilder2005, 
~/.primetime2005 and ~/.borland (also ~/.qualitycentral, but it's empty). 
We install templates (stored in files:
/mit/jbuilder_v2005/distrib/$ATHENA_SYS/$ATHENA_SYS.jbuilder2005.tar 
/mit/jbuilder_v2005/distrib/$ATHENA_SYS/$ATHENA_SYS.primetime2005.tar
/mit/jbuilder_v2005/distrib/$ATHENA_SYS/$ATHENA_SYS.borland.tar
created manually from a fresh "first launch" and use sed to write in the 
home dir into the one file in .primetime2005 ~/.primetime2005/user.properties
in place of the actual home dir.

In addition, file "java version 1.4.2_04-b05.library" in .jbuilder2005 will
have paths to components in the locker that are obviously incorrect; although
JBuilder still seems to run with these incorrect paths, we edit them to the
correct values before building the tar archives.

The local configuration files are platform-dependent, so we separate
these by architecture. Initially, the local configuration directory
size is quite small (about 30k). Symlinks from .jbuilder2005, .primetime2005
and .borland to the correct platform-dependent versions 
(.jbuilder2005.$ATHENA_SYS, .primetime2005.$ATHENA_SYS and .borland.ATHENA_SYS)
is made at run-time.

The ant package (jb2005_fnd_extras.zip) is platform-independent but requires
special configuration steps. We install it in ...distrib/share/ant. Make ant
and antRun in src/script dir, and bootstrap.sh and build.sh at top level
executable, set JAVA_HOME to 
/mit/jbuilder_v2005/distrib/sun4x_59/JBuilder2005/jdk1.4 and run build.sh.
..share/ant/bootstrap/bin/ant will be run script; add lines to it, near top:

locker="jbuilder_v2005"
ANT_HOME=/mit/${locker}/distrib/share/ant/bootstrap
JAVA_HOME=`athdir -f "/mit/${locker}/distrib/%s/JBuilder2005/jdk1.4"`
export JAVA_HOME
export ANT_HOME

and make links to this script from /mit/jbuilder_v2005/arch/$ATHENA_SYS/bin and
/mit/jbuilder_v2005/distrib/$ATHENA_SYS/JBuilder2005/bin

The default ant home seems to be preset at ...JBuilder2005/thirdparty/ant; to
get around this we make a link: 
...JBuilder2005/thirdparty/ant -> ../../../share/ant/bootstrap

We install pdf documentation from jb2005pdfdocs_f.zip into
/mit/jbuilder_v2005/distrib/share/doc

    MAKING CHANGES

    SPECIAL NOTES

Application comes with a built-in 1.4.2_04 JDK.

We make redirects for release_notes.html, whatsnew.html, and a link for
license.html in /mit/jbuilder_v10/www.

We add an optional autosave.jar that we put in
$ATHENA_SYS/JBuilder2005/lib/ext. Source is at
http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=15844

On Suns, parameter vmmemmax in file JBuilder2005/bin/jbuilder.config
needs to be commented out to prevent launch error:

Invalid maximum heap size: -Xmx-1575m
Unable to create JVM.

This is apparently due to large amount of memory present in newer models.

MAINTENANCE NOTES:
	
    TUTORIAL

There is a built-in tutorial and sample projects (we install both the 
documentation and extra sample projects). The opening screen has links
to the tutorial and release notes.