Obtaining Pluto 1.1/2.0 Source Code

The Pluto project uses the Subversion version control system. If you're new to Subversion, you can check out the online book about Subversion. Note that we are currently using Subversion 1.3.x (there are separate versions of the book covering the different versions of Subversion).

Web Access to Subversion

To browse the Pluto source code, you can use the ViewCVS web interface to Subversion. This is current at all times.

Normal Subversion Access

Anyone can check code out of Subversion anonymously. However, you need to specify a username and password in order to update the Subversion repository, and only Pluto committers have the permissions to do that. We run Subversion over standard HTTPS, so hopefully you won't have problems with intervening firewalls.

Check out from Subversion

Again, anyone can do this. To check out the latest distribution of Pluto 2.0 (trunk) to a directory called 'pluto' use this command:

svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ pluto

To check out Pluto 1.1.x source to the 'pluto' directory use this command (substituting 'x' for the current release number, e.g. 1.1.5):

svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.x pluto

Zipped up Pluto 1.1 source distributions can also be downloaded from a distribution mirror.

Building Pluto with Maven 2

If this is your first time building Pluto with Maven 2, edit ~/.m2/settings.xml and add the <pluginGroups> element:

<settings>
  ...
  <pluginGroups>
    <pluginGroup>org.apache.pluto</pluginGroup>
  </pluginGroups>
  ...
</settings>
            

<PLUTO_SRCHOME> is the local directory where the Pluto 1.1/2.0 source distribution has been checked out or unzipped into.

$> cd <PLUTO_SRCHOME>
$> mvn install
$> mvn pluto:install -DinstallDir=path/to/appserver
          

The install goal is a built in Maven 2 lifecycle which builds the project artifacts and installs them into the Maven repository.

The pluto:install goal will take the resulting artifacts and properly deploy them within the configured Tomcat installation. Currently, the Pluto install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20, 5.5.23, and 6.0.13. The Tomcat 5 archive can be found here.

If installing to a directory that contains spaces, installDir needs to be enclosed within quotes:

C:\pluto> mvn pluto:install -DinstallDir="C:\Program Files\Apache Software Foundation\Tomcat 5.5"
          

Installing Pluto Manually

This section documents the manual installation of Pluto 1.1 and 2.0 into Tomcat. It replaces the pluto:install goal, but requires that the built-in Maven 2 install goal (mvn install) be run from <PLUTO_SRCHOME>.

Step 1:

$> cd <PLUTO_SRCHOME>
$> mvn install
          

Step 2: Copy the following to <TOMCAT_HOME>/shared/lib:

• activation-1.1.jar (Pluto 2.0 only)
• castor-1.1.1.jar (Pluto 1.1.x only)
• portlet-api-1.0.jar or portlet-api-2.0.jar
• jaxb-api-2.1.jar (Pluto 2.0 only)
• jaxb-impl-2.1.2.jar (Pluto 2.0 only)
• ccpp-1.0.jar (Pluto 2.0 only)
• stax-1.2.0.jar (Pluto 2.0 only)
• stax-api-1.0.1.jar (Pluto 2.0 only)
• xercesImpl-2.6.2.jar (Pluto 2.0 only)
• xmlParserAPIs-2.6.2.jar (Pluto 2.0 only)
• pluto-container-x.x.x.jar (x.x.x is the version of Pluto you built)
• pluto-descriptor-api-x.x.x.jar (x.x.x is the version of Pluto you built)
• pluto-descriptor-impl-x.x.x.jar (x.x.x is the version of Pluto you built)
• pluto-taglib-x.x.x.jar (x.x.x is the version of Pluto you built)

Step 3: For platforms running on Java 1.4 and Pluto 1.1, copy the following to <TOMCAT_HOME>/common/endorsed (if you are running Java 1.5+, or you are running Pluto 2.0, it is recommended to skip this step):

• xercesImpl-2.6.2.jar
• xmlParserAPIs-2.6.2.jar

Step 4: Copy the following to <TOMCAT_HOME>/conf/Catalina/localhost:

• <PLUTO_SRCHOME>/pluto-portal/src/main/resources/pluto.xml
• <PLUTO_SRCHOME>/pluto-testsuite/src/main/resources/testsuite.xml

Step 5: Copy the following to <TOMCAT_HOME>/webapps:

• <PLUTO_SRCHOME>/pluto-portal/target/pluto-portal.war
• <PLUTO_SRCHOME>/pluto-testsuite/target/pluto-testsuite.war

Configuring Source-Built Pluto for Application Scope PortletSession Attributes

To be able to use application-scoped PortletSession attributes in Pluto, modify the Connector element for port 8080 in <TOMCAT_HOME>/conf/server.xml by adding the following attribute and value: emptySessionPath="true".

Configuring User and Role in the Pluto Source Build

The Pluto Testsuite portlet application needs the role 'pluto' to run the Security Mapping Test. So before starting tomcat, you should edit <TOMCAT_HOME>/conf/tomcat-users.xml, add the role 'pluto', and add a user in that role. The simplest way to do this is to edit add the 'pluto' role to the 'tomcat' user's record. Here is a sample tomcat-users.xml file:

<?xml version="1.0" encoding="utf-8"?>
<tomcat-users>
  <role rolename="manager"/>
  <role rolename="pluto"/>
  <role rolename="tomcat"/>
  <role rolename="role1"/>
  <user username="tomcat" password="tomcat" roles="tomcat,pluto,manager"/>
  <user username="role1" password="tomcat" roles="role1"/>
  <user username="both" password="tomcat" roles="tomcat,role1"/>
  <user username="pluto" password="pluto" roles="pluto,manager"/>
</tomcat-users>
        

Starting the Portal

Now you are ready to use the Pluto Portal built from source. Start up tomcat by running startup.bat (for windows) or startup.sh (for *nix) in <TOMCAT_HOME>/bin, and browse to http://localhost:8080/pluto/portal. Login to Pluto using the user and password you just created in tomcat-users.xml. If you added the 'pluto' role to the 'tomcat' user's record, you can login as 'tomcat/tomcat'.