System Requirements to Run Jetspeed 2.3.1:
Where you start depends on what you plan on doing with Jetspeed. Its always best to start by reading the documentation guides. There are several guides provided:
For those of you in more of a hurry to get started, you have the choice of installing Jetspeed from a binary release or doing more indepth open source development by working with the source code.
If you want to modify the core functionality of Jetspeed or contribute to the development of Jetspeed, you need to work with the source code. If you are interested in building your first custom enterprise portal, try the custom build. We recommend trying an Evaluation (demo, download) to get started. Eventually you will want to move on to Building a Custom Portal. Advanced users will want to learn how to build from source.
If you are evaluating Jetspeed, best to download the latest distribution or try running Jetspeed from the demo site:
Download Requirements - The requirements for the downloadable distribution are: Java 1.5 or higher, enough memory to run Tomcat with several web apps (the demo comes with Tomcat embedded in the installer)
Online Demo Requirements - The requirements for the online demos are minimal: just a web browser
When starting a new Jetspeed portal project, we strongly recommend that you create a custom portal project, and do not edit the Jetspeed-2 source and resources directly. A custom build allows you to create and maintain a Jetspeed Portal's lifecycle. With a custom build, you have a reproducible procedure for maintaining your portal across future versions. When we say custom, we mean customizing Jetspeed for your needs. Everyone has custom requirements. Custom build procedures formalize the steps required to create a custom portal. Although Jetspeed can be customized online using the portal customization features. Still, having a reproducible build is valuable as it enables you to store artifacts in a source code repository and maintain the life-cycle of this source.
Custom Jetspeed builds for version 2.3.1 are built with Maven-3 only. (The Maven-1 custom build is no longer supported.) Building Jetspeed from source is not necessary for most projects.
The Maven Custom Build is based on a Maven plugin. To get started with the Maven plugin, see the documentation here:
General requirements for custom builds:
Jetspeed is distributed with the Derby database configured as the default.
The database configuration will be setup during the custom build process based on your property settings. See the appropriate build guide for details.. If you are not going to use the default Derby database, you need to select another database during your build configuration.
Building from Source is covered in the Developer guide. We build Jetspeed with Maven-2.
The best place to start using Jetspeed, as a Developer, is to go to the developers guide documentation:
For general build information, also see the Jetspeed Build Guide: