 |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
<-- The following statements are not true until the new MyJxta? Project pages are completed -->
| | | -- Main.mcangus - 04 May 2008
-- Main.mcangus - 13 Jun 2004
-- Main.mcangus - 10 Jun 2004
|
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
| |
>
> | <-- The following statements are not true until the new MyJxta? Project pages are completed -->
If you wish to obtain the latest/greatest codebase you are encouraged to try the following process as generally described in BuildingJXTA: | | | prerequsites: | |
<
< |
On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS.
Don't forget to add the path to the command line executable (e.g. <winCVS install dir>\CVSNT for WinCVS) to your PATH environment variable.
On Windows and Mac OS X, you may receive an error similar to the following when you try to follow the installation instructions below:
[cvs] cvs checkout: could not open <cvs home path>/.cvspass: No such file or directory
[cvs] cvs [checkout aborted]: use "cvs login" to log in first
If so, you need to create and prime your .cvspass file by entering the following at a command line (Windows: command window, Mac: Terminal):
cvs -d :pserver:guest@cvs.jxta.org:/cvs login
When promted for a password, simply hit the Enter/Return key (the guest user has no passowrd). | >
> |
- J2SDK 1.5.0+
- Ant 1.6+
- Subversion (Subversion client)
| | | With the above prerequisites installed and availble in your system environment, create a workspace: | | | % cd jxta
| |
<
< | Windows 2000: | >
> | Windows 2000/XP/Vista: | | |
> mkdir %USERPROFILE%\jxta
> cd %USERPROFILE%\jxta | | | % ant -f install.xml
| |
>
> | -- Main.mcangus - 04 May 2008
| | | -- Main.mcangus - 13 Jun 2004
-- Main.mcangus - 10 Jun 2004
-- JamesTodd - 21 Mar 2004 |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | | At this point you should have a working copy of MyJXTA: | |
<
< | % cd myjxta2/binding/java | >
> | % cd myjxta2 | | | % ant run
|
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | |
On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS. | |
<
< | Don't forget to add the path to the command line executable (e.g. <winCVS install dir>\CVSNT for WinCVS?) to your PATH environment variable. | >
> | Don't forget to add the path to the command line executable (e.g. <winCVS install dir>\CVSNT for WinCVS) to your PATH environment variable. | | | On Windows and Mac OS X, you may receive an error similar to the following when you try to follow the installation instructions below: |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | |
On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS. | |
<
< | Don't forget to add the command line executable (e.g. <winCVS install dir>wincvs.exe) to your PATH environment variable. | >
> | Don't forget to add the path to the command line executable (e.g. <winCVS install dir>\CVSNT for WinCVS?) to your PATH environment variable. | | | On Windows and Mac OS X, you may receive an error similar to the following when you try to follow the installation instructions below: | | | % ant -f install.xml
| |
>
> | -- Main.mcangus - 13 Jun 2004
| | | -- Main.mcangus - 10 Jun 2004
-- JamesTodd - 21 Mar 2004 | |
>
> | |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | | Ant 1.6+
| |
<
< | On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS.
| >
> | On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS. | | | Don't forget to add the command line executable (e.g. <winCVS install dir>wincvs.exe) to your PATH environment variable.
On Windows and Mac OS X, you may receive an error similar to the following when you try to follow the installation instructions below: |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | | Ant 1.6+
| |
>
> | On Windows, you will also need to add a CVS Client with command line capabilities. One option is WinCVS.
Don't forget to add the command line executable (e.g. <winCVS install dir>wincvs.exe) to your PATH environment variable.
On Windows and Mac OS X, you may receive an error similar to the following when you try to follow the installation instructions below:
[cvs] cvs checkout: could not open <cvs home path>/.cvspass: No such file or directory
[cvs] cvs [checkout aborted]: use "cvs login" to log in first
If so, you need to create and prime your .cvspass file by entering the following at a command line (Windows: command window, Mac: Terminal):
cvs -d :pserver:guest@cvs.jxta.org:/cvs login
When promted for a password, simply hit the Enter/Return key (the guest user has no passowrd). | | | With the above prerequisites installed and availble in your system environment, create a workspace: | |
>
> | *nix or Mac OS X: | | |
% mkdir ~/jxta
% cd jxta
| |
<
< | note: the above process can be replicated for non *nix based systems as needed. | >
> | Windows 2000:
> mkdir %USERPROFILE%\jxta
> cd %USERPROFILE%\jxta
note: the above process can be replicated for other systems as needed. | | | Next, obtain a working copy of the "JXTA Bootstrapper" by copying the bootstrap.xml file locally. Alternatively, you can copy the following text into a file named "bootstrap.xml" to achieve the same results: | | | % ant -f install.xml
| |
>
> | -- Main.mcangus - 10 Jun 2004
| | | -- JamesTodd - 21 Mar 2004 | |
>
> | |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | | Ant 1.6+
| |
<
< | With the above prereq installed and availble in your system environment, create a workspace: | >
> | With the above prerequisites installed and availble in your system environment, create a workspace: | | |
% mkdir ~/jxta | | | Next, obtain a working copy of the "JXTA Bootstrapper" by copying the bootstrap.xml file locally. Alternatively, you can copy the following text into a file named "bootstrap.xml" to achieve the same results: | |
<
< | | >
> |
| | | | |
<
< | | >
> | | | |
| |
<
< | <get src="${http.url}"
dest="./install.xml"
usetimestamp="true"/> | >
> | | | | | |
<
< | <ant antfile="install.xml"
inheritAll="false"/> | >
> | | | |
|
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page. | | | | |
<
< | | >
> | | | | <get src="${http.url}"
dest="./install.xml"
usetimestamp="true"/> | | | % ant -Dcvs.project=myjxta2 -f bootstrap.xml
| |
<
< | At this point you should have a working copy of the relevant JXTA project. The above process can be executed as needed to refresh your local workspace. You can then run a local copy of MyJXTA as follows: | >
> | At this point you should have a working copy of MyJXTA: | | |
% cd myjxta2/binding/java
% ant run
| |
>
> | The install process can be executed as needed to refresh your local workspace:
% ant -f install.xml
| | | -- JamesTodd - 21 Mar 2004 |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
| |
<
< | | | | The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page.
If, on the other hand, you wish to obtain the latest/greatest codebase you are encouraged to try the following | | | % ant -Dcvs.project=myjxta2 -f bootstrap.xml
| |
<
< | At this point you should have a working copy of the relevant JXTA project. The above process can be executed as needed to refresh your local workspace. You can then run a local copy of MyJXTA as follows: | >
> | At this point you should have a working copy of the relevant JXTA project. The above process can be executed as needed to refresh your local workspace. You can then run a local copy of MyJXTA as follows: | | |
% cd myjxta2/binding/java |
| |
| META TOPICPARENT | name="MyJXTA" |
|---|
| |
>
> | | | | The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page.
If, on the other hand, you wish to obtain the latest/greatest codebase you are encouraged to try the following |
|
>
> |
| META TOPICPARENT | name="MyJXTA" |
|---|
The easiest way to obtain MyJXTA's source is to pull the relevant source distribution from the MyJXTA Home Page.
If, on the other hand, you wish to obtain the latest/greatest codebase you are encouraged to try the following
process as generally described in BuildingJXTA:
prerequsites:
With the above prereq installed and availble in your system environment, create a workspace:
% mkdir ~/jxta
% cd jxta
note: the above process can be replicated for non *nix based systems as needed.
Next, obtain a working copy of the "JXTA Bootstrapper" by copying the bootstrap.xml file locally. Alternatively, you can copy the following text into a file named "bootstrap.xml" to achieve the same results:
<?xml version="1.0" encoding="utf-8""?>
<project name="jxta installer" basedir="." default="installer"/>
<property name="http.url" value="http://download.jxta.org/commons/install.xml"/>
<target name="installer" description="obtain jxta intall">
<get src="${http.url}"
dest="./install.xml"
usetimestamp="true"/>
<ant antfile="install.xml"
inheritAll="false"/>
</target>
</project>
Lastly, execute the bootstrapper as follows:
% ant -Dcvs.project=myjxta2 -f bootstrap.xml
At this point you should have a working copy of the relevant JXTA project. The above process can be executed as needed to refresh your local workspace. You can then run a local copy of MyJXTA as follows:
% cd myjxta2/binding/java
% ant run
-- JamesTodd - 21 Mar 2004 |
|