As Ken has suggested I am trying to study the glassfish code to get a better
idea of how JSFT is supposed to work.
Ok, I have observer status for the glassfish project and am looking at the
instructions at this url:
https://glassfish.dev.java.net/public/BuildGlassFish.html#configuration
First of all, it says you have to have the latest updates of Java 5, which
is currently release 11. My understanding is that if I have the java update
icon in my control panel and I have it set for automatic updates, then I
should have all the latest updates, even if I haven't actually downloaded
release 11. Have I got that right or do I need to explicitly download the
latest release?
Also, I am a bit confused by the following section:
GlassFish build steps:
The first step is to checkout the module dependencies and common files used
in the build system and edit the properties file.
% mkdir workspace
% cd workspace
% cvs -d :pserver:<userid>@cvs.dev.java.net:/cvs checkout glassfish/bootstrap
This will checkout project.xml, maven.xml, project.properties, and
common files referenced from project.xml.
Create workspace/glassfish/bootstrap/build.properties or for re-usable
GlassFish workspace, one-time process is to create ${HOME}/build.properties
(Unix) or %HOMEPATH%\build.properties (Windows) and set following
variables: (you can get %HOMEPATH% value by running the command: echo
%HOMEPATH% or run "set" and find HOMEPATH variable (windows))
Note that I am running Win XP and have downloaded Maven. As instructed under
the java.net cvs setup, I have setup wincvs and have a main directory for
CVS projects. Can I use Wincvs with Maven or do I have to use command-line
cvs? Should the workspace directory be under that or does it need to be at
the root of my directory. The above instructions aren't specific about this.
Also, it is not clear on how to create build.properties. Is it just a blank
text file or what? What is the advantage of putting it in the HOMEPATH?
Then ther is step 2:
1. Bootstrap the server image (a collection of scripts and jar files
used to run glassfish). Developer can select the option of "bootstrap" which
downloads the pre-built server and builds only subset of the modules. Other
option "bootstrap-all" is to create the server from scratch, and build all
the modules to verify the intermodule or binary dependencies version change.
*bootstrap-all* option: Building all the modules from the source.
% maven bootstrap-all
*bootstrap* option: Build your own module using pre-built server
% maven bootstrap
This step is optional if you have already installed a promoted build
of GlassFish. To use the promoted build you will need to set the property
in glassfish/project.properties.
glassfish.image.version=<<build version>>
This will cause the build system to "point" to that installation. This
property can also be added to ${HOME}/build.properties
When is says " This step is optional if you have already installed a
promoted build of GlassFish." is it referring to everything under step 2?
What is a "promoted build"? I currently have a version of Sun AppServer PE9
running, does that qualify? How do I find the "build version" used to set
the version property? Are there any "gotchas" with building glassfish if you
have Sun AppServer installed?
Thanks in advance for your help.