1. Java SE JDK 5.0

1. Subversion (svn client)

1. JDK 5.0
2. Ant 1.6.3+
3. Subversion (cvs client)

1. CVS (cvs client)

1. J2SDK 1.4.2+
2. Ant 1.6+

  % ant -Dcvs.project=myjxta2 -f bootstrap.xml

  % cd myjxta2/binding/java
  % ant run

The associated MyJXTA ant.properties is as follows:

1. J2SDK 1.4.1+ (1.4.2 prefered)
2. Ant 1.5.4+ (1.6+ prefered)

1. Ant 1.6+

<?xml version="1.0" encoding="utf-8"?>

<project name="jxta install" basedir="." default="install">

  <property name="cvs.project" value="shell"/>
  <property name="cvs.version" value=""/>
  <property name="cvs.user" value="guest"/>
  <property name="cvs.server" value="cvs.jxta.org"/>
  <property name="cvs.directory" value ="${cvs.project}"/>
  <property name="cvs.destination" value="."/>

  <target name="install" description="project installation">
    <cvs command="checkout -d ${cvs.directory}"
             cvsRoot=":pserver:${cvs.user}@${cvs.server}:/cvs"
             package="${cvs.project}"
             tag="${cvs.version}"
             dest="${cvs.destination}"/>

     <ant antfile="build.xml"
             dir="${cvs.destination}/${cvs.directory}/binding/java"
             target="bootstrap"
             inheritAll="false"/>
  </target>
</project>

Taking into consideration the above script one can build and run a JXTA project as follows:

  # create work environment
  % mkdir projects
  % cd projects
  # procure installation script
  % cp {install.xml} .
  # install
  % ant -f install.xml
  # run
  % cd {project}/binding/java
  % ant run

The install script defaults can be overridden to manage any core JXTA project, eg:

  % ant -Dcvs.project=myjxta2 -Dcvs.version=JXTA_2_2_1_STABLE -f install.xml
  % cd myjxta2/binding/java
  % ant run

1. J2SDK 1.4+

So HowToBuildUsingJBuilder^? HowToBuildUsingNetBeans HowToBuildUsingJEdit^? HowToBuildUsingEclipse

-- HugoGarcia - 22 Sep 2003

1. J2SDK 1.3.1+
2. Ant 1.5.1+

Using Ant, obtaining, building and running most Core JXTA projects is as easy 1 2 3:

  # create work environment
  % mkdir projects
  % cd projects
  # obtain the source code
  % cvs -d :pserver:guest@jxta.org:/cvs co shell
  % cd shell/binding/java
  # build
  % ant bootstrap
  # run
  % ant run

Well, as easy as 1 2 3 4 ... but you get the idea.

The above example checks out a read-only local copy of the main branch (aka trunk) of the Shell project. Substituting the "guest" user with your JXTA Member ID enables you to check out a commiter (i.e. read-write) work space. Further, in order to build a "tagged" branch the following modifications are required:

  # create work environment
  % mkdir projects
  % cd projects
  # obtain the source code
  % cvs -d :pserver:guest@jxta.org:/cvs co -r JXTA_2_1_1_STABLE -d shell-JXTA_2_1_1_STABLE shell
  % cd shell-JXTA_2_1_1_STABLE/binding/java
  # build
  % ant bootstrap
  # run
  % ant run

An alternative, albeit untested, option is as follows (technically this should work):

 
  # create work environment
  % mkdir projects
  % cd projects
  # obtain the source code
  % cvs -d :pserver:guest@jxta.org:/cvs co -r JXTA_2_1_1_STABLE -d shell-JXTA_2_1_1_STABLE shell
  % cd shell-JXTA_2_1_1_STABLE/binding/java
  # build
  % ant -Dtag=JXTA_2_1_1_STABLE bootstrap
  # run
  % ant run

Lastly, litterally all JXTA build properties can be overridden by placing a valid "ant.properties" file in any one or more of the following locations:

  {JXTA root}/.ant.properties (e.g. peer to shell)
  {JXTA project}/.ant.properities (e.g. [JXTA root}/shell/binding/java/.ant.properties)
  {user.home}/.ant.properties (e.g. ~/.ant.properties)

The first option, in the "JXTA root," is preferable as it has a larget scope and is not necessarily mixed up with other user "dot" files. A more extreme example of checking out and building a "tagged" branch is as follows:

  # create work environment
  % mkdir projects
  % cd projects
  # create .ant.properties
  % echo "security.dir=../../../security
platform.dir=../../../platform
shell.dir=../../../shell
cms.dir=../../../cms" > .ant.properties
  # obtain the source code
  % cvs -d :pserver:guest@jxta.org:/cvs co -r JXTA_2_1_1_STABLE -d shell-JXTA_2_1_1_STABLE shell
  % cd shell-JXTA_2_1_1_STABLE/binding/java
  # build
  % ant -Dtag=JXTA_2_1_1_STABLE bootstrap
  # run
  % ant run

The above is just one example of a valid "ant.properties" file.

-- JamesTodd - 03 Sep 2003