The extension environment is build around a set of ant build scripts that are highly configurable through properties files and build scripts. You should create customized versions of the properties files by creating a version with the same name than the original one but inserting your user name before the extension. The two most important files that should be customized are:
app.server.${user.name}.properties: set
the application server that you are going to use. For
example:
app.server.type=jboss-jetty
Read app.server.properties to find
other properties whose values you may want to override.
build.${user.name}.properties: in this
file you can set the compiler you want to use (the default is
jikes), the amount of memory that it will have, some extra class
paths, specific WARs that you may want to deploy, etc. Here is an
example that sets these properties:
javac.compiler=modern javac.debug=off javac.memoryMaximumSize=128m classpath.ext=/sharedlibs/mycompanylib.jar deploy.specific.wars=/sharedportlets/mycompanyportlet.war
You can also set the property
jsp.precompile to on in
build.properties to precompile JSPs if you
are using Jetty, JBoss+Jetty, JBoss+Tomcat, JOnAS+Jetty (other AP.
servers do not support this functionality) . This takes a few
minutes and should only be used when deploying to a production
server.
Read build.properties to look for other
properties that you might be interested in overriding.
If the customization options provided by the properties files is
not enough you can extend the environment by writing your own build
scripts. To make this possible all default targets are written in
files called build-parent.xml that are inherited
from the file that ant will actually look for
(build.xml). You can modify all script files
named build.xml and add your own targets or
override the default ones. When the extension environment is upgraded
your modified files will be preserved.