You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@portals.apache.org by at...@apache.org on 2012/12/16 23:55:26 UTC
svn commit: r1422709 [25/44] - in /portals/site-live/jetspeed-2.1.3:
2.1/schemas/ adminguide/ adminguide/css/ adminguide/images/
adminguide/images/logos/ css/ deployguide/ deployguide/css/
deployguide/images/ deployguide/images/ldap/ deployguide/images...
Added: portals/site-live/jetspeed-2.1.3/devguide/m2-build/j2-maven-plugin.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/devguide/m2-build/j2-maven-plugin.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/devguide/m2-build/j2-maven-plugin.html (added)
+++ portals/site-live/jetspeed-2.1.3/devguide/m2-build/j2-maven-plugin.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,259 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Jetspeed 2 Enterprise Portal - Jetspeed 2 Maven Plugin</title><style type="text/css" media="all">
+ @import url("../../style/maven-base.css");
+
+ @import url("../../style/maven-j2.css");@import url("../../style/project.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://portals.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://portals.apache.org/images/apache-portals.gif"></img></a><a href="http://portals.apache.org/jetspeed-2" id="projectLogo"><img alt="Jetspeed 2 Enterprise Portal" src="http://portals.apache.org/images/Jetspeed_blue_med.png"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+ Last published: 23 April 2009
+ | Doc for 2.1.3</div><div class="xright">
+
+ <a href="../../usersguide/index.html">Users Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../adminguide/index.html">Admin Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../deployguide/index.html">Deployers Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../devguide/index.html">Developers Guide</a>
+ </div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuEssentials"><h5>Essentials</h5><ul><li class="none"><a href="../../index.html">Welcome</a></li><li class="none"><a href="../../features.html">Features</a></li><li class="none"><a href="../../getting-started.html">Getting Started</a></li><li class="none"><a href="../../demo.html">Jetspeed Online Demos</a></li></ul></div><div id="menuGet_Jetspeed-2_1_3"><h5>Get Jetspeed-2.1.3</h5><ul><li class="none"><a href="../../download.html">Download</a></li><li class="none"><a href="../../getting-started-installer.html">Installer Instructions</a></li><li class="none"><a href="../../release-notes.html">Release Notes</a></li></ul></div><div id="menuDocumentation_Guides"><h5>Documentation Guides</h5><ul><li class="none"><a href="../../usersguide/index.html">Users Guide</a></li><li class="none"><a href="../../adminguide/index.html">Administrators Guide</a></li><li class="none"><a href=".
./../deployguide/index.html">Deployment Guide</a></li><li class="none"><a href="../../devguide/index.html">Developers Guide</a></li><li class="none"><a href="../../guide-migration.html">Migration Guide</a></li></ul></div><div id="menuAPIs"><h5>APIs</h5><ul><li class="none"><a href="../../multiproject/jetspeed-api/apidocs/index.html">Jetspeed-2 Java API</a></li><li class="none"><a href="../../devguide/guide-ajax-api.html">Jetspeed-2 AJAX API</a></li><li class="none"><a href="../../devguide/j2-maven-plugin.html">Jetspeed-2 Maven-2 Plugin</a></li></ul></div><div id="menuTutorials"><h5>Tutorials</h5><ul><li class="none"><a href="../../tutorials/maven-2/index.html">Jetspeed Tutorial - Maven-2 Custom Build</a></li><li class="none"><a href="../../tutorials/ant/index.html">Jetspeed Tutorial - Ant Custom Build (incomplete)</a></li><li class="none"><a href="../../tutorials/stepbystep/guide-building-custom-portal-maven1.html">Maven-1 Custom Build</a></li><li class="none"><a href="../..
/tutorials/stepbystep/guide-building-custom-portal-maven2.html">Maven-2 Custom Build</a></li></ul></div><div id="menuAbout_Jetspeed-2"><h5>About Jetspeed-2</h5><ul><li class="none"><a href="../../j1-users.html">For Jetspeed-1 Users</a></li><li class="none"><a href="../../j1-migration.html">Jetspeed-1 Migration Guideline</a></li><li class="none"><a href="../../supporting-projects.html">Supporting Projects</a></li><li class="none"><a href="../../who-uses-j2.html">Who Uses J2?</a></li><li class="none"><a href="../../portlets-community.html">Portlets Community</a></li><li class="none"><a href="../../how-to-help.html">How to Help?</a></li></ul></div><div id="menuSupport"><h5>Support</h5><ul><li class="none"><a href="../../mail-lists.html">Mailing List</a></li><li class="none"><a href="../../issue-tracking.html">Bug Database</a></li><li class="none"><a href="http://wiki.apache.org/portals/Jetspeed2" class="externalLink" title="External Link">Wiki</a></li><li class="none"><a href="
../../faq.html">FAQ</a></li></ul></div><div id="menuTranslation"><h5>Translation</h5><ul><li class="none"><a href="http://jetspeed-japan.sourceforge.jp/jetspeed-2-trans/ja/index.html" class="externalLink" title="External Link">Japanese</a></li></ul></div><div id="menuProject_Documentation"><h5>Project Documentation</h5><ul><li class="none"><a href="../../index.html">About Jetspeed 2 Enterprise Portal</a></li><li class="collapsed"><a href="../../project-info.html">Project Info</a></li><li class="collapsed"><a href="../../maven-reports.html">Project Reports</a></li><li class="none"><a href="http://maven.apache.org/development-process.html" class="externalLink" title="External Link">Development Process</a></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Maven-2_Plugin_Overvi
ew"></a><h2>Maven-2 Plugin Overview</h2><p>
+ Adding functionality to Maven is done through the Maven plugin mechanism. Maven comes shipped with numerous
+ plugins and provides an extensible framework for writing custom plugins.
+ Details on custom Maven plugins can be found in the
+ <a href="http://maven.apache.org/using/developing-plugins.html" class="externalLink" title="External Link">Writing a Plugin</a> section of Maven's web
+ site.
+ </p><p>
+ Jetspeed 2 has developed a custom Maven plugin that centralizes most common build goals required to build a
+ Jetspeed 2 based portal application. This provides many benefits:
+ </p><ul>
+ <li>
+ Better reusability of common build goals. Developers creating a new portal application can leverage the
+ Jetspeed 2 Maven plugin for common build operations.
+ </li>
+ <li>
+ The ability to quickly get started with a portal application. With the goal <code>j2:portal.genapp</code>
+ a new portal application can be created. The developer of the new application can reuse the Jetspeed 2
+ Maven plugin goals for common build operations for quickStart, portlet deployment, etc.
+ </li>
+ <li>
+ Preparation for future migration to Maven 2 (M2). With M2, custom goals are encapsulated in plugins, maven.xml
+ is deprecated. By centralizing most of the Jetspeed 2 build goals to the Jetspeed 2 Maven plugin, migration to
+ M2 should be much easier.
+ </li>
+ </ul></div><div class="section"><a name="Portal_Application_creation_and_configuration_Goals"></a><h2>Portal Application creation and configuration Goals</h2><div class="subsection"><a name="Creating_a_new_Portal_Application"></a><h3>Creating a new Portal Application</h3><table class="bodyTable"><tr class="a"><th>Goal</th><th>Description</th></tr><tr class="b"><td><code>j2:portal.genapp</code></td><td>
+ Generates or updates a custom portal application. Checkout the
+ <a href="getting-started.html#4__Creating_a_new_Portal_Application">Getting Started</a>
+ document for basic usage of this goal.
+ <br></br>
+ </td></tr><tr class="a"><td><code>j2:portal.genapp.minimal</code></td><td>
+ Works similar to <code>j2:portal.genapp</code>. However, it
+ will only copy the following directories/files from <code>WEB-INF/pages</code>.
+ <ul>
+ <li>/WEB-INF/pages/Administrative/** (all contents)</li>
+ <li>/WEB-INF/pages/page.security</li>
+ </ul>
+ </td></tr></table></div><div class="subsection"><a name="Configuring_and_updating_a_Portal_Application"></a><h3>Configuring and updating a Portal Application</h3><p>
+ The <code>j2:portal.genapp</code> goal above is actually no more than a wrapper around several (sub)goals
+ which can also be used individually to update and configure your portal application:
+ </p><table class="bodyTable"><tr class="b"><th>Goal</th><th>Description</th></tr><tr class="a"><td><code>j2:portal.copy.webapp</code></td><td>
+ Copies the (static) Jetspeed 2 portal web resource from the plugin to the
+ <code>${org.apache.jetspeed.portal.webapp.dir}</code> folder.
+ <br></br>
+ <br></br>
+ Running this goal again will not clear out previous resources but <i>will</i> overwrite existing resources.
+ <br></br>
+ <br></br>
+ If you need to upgrade to a newer version of the Jetspeed 2 portal you should clear out these resources
+ yourself first. By default, the target folder is configured within the maven default target folder and
+ running the <code>clear</code> goal will do exactly that.
+ </td></tr><tr class="b"><td><code>j2:portal.copy.webapp.minimal</code></td><td>
+ Similar to <code>j2:portal.copy.webapp</code> However, it
+ will only copy the following directories/files from <code>WEB-INF/pages</code>.
+ <ul>
+ <li>/WEB-INF/pages/Administrative/** (all contents)</li>
+ <li>/WEB-INF/pages/page.security</li>
+ </ul>
+ </td></tr><tr class="a"><td><code>j2:portal.conf.project</code></td><td>
+ Creates a new maven or updates an existing portal project configuration in the
+ <code>${org.apache.jetspeed.portal.home.dir}</code> folder.
+ <br></br>
+ It creates a hiearchy of 5 maven project files:
+ <ul>
+ <li><code>project-info.xml</code></li>
+ <li><code>core-build.xml extends project-info.xml</code></li>
+ <li><code>jetspeed-components.xml extends core-build.xml</code></li>
+ <li><code>full-portal.xml extends jetspeed-components.xml</code></li>
+ <li><code>project.xml extends full-portal.xml</code></li>
+ </ul>
+ Of the above files, the first and the last (project-info.xml and project.xml) may be modified to provide
+ additional project information and configuration and will not be updated by this goal again. Only the
+ other 3 files will be rewritten by this goal. If you need to upgrade to a newer version of the Jetspeed 2
+ portal your own customization will be preserved.
+ <br></br>
+ <br></br>
+ Additionally, you can add your own maven.xml and/or project.properties or build.properties to further
+ customize your portal. These also will be preserverd when you run this goal again.
+ </td></tr><tr class="b"><td><code>j2:portal.conf.sql</code></td><td>
+ Generates the portal sql schema DDL for the configured database(s) under the
+ <code>${org.apache.jetspeed.portal.sql.dir}</code>, as well as copies over statically defined common and
+ selected database specific sql DML and DDL (possibly overriding generated DDL).
+ <br></br>
+ <br></br>
+ The content of the sql target folder is cleared out first when this goal is run.
+ </td></tr><tr class="a"><td><code>j2:portal.conf.ojb</code></td><td>
+ Copies the OJB configuration, filtered for the currently selected production database to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ <br></br>
+ <br></br>
+ As default, the above target folder is configured under the default maven war target folder. The maven
+ <code>clear</code> goal will also remove this filtered OJB configuration.
+ </td></tr><tr class="b"><td><code>j2:portal.conf.ldap</code></td><td>
+ Copies the LDAP configuration, to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ </td></tr><tr class="a"><td><code>j2:portal.conf.jetspeed</code></td><td>
+ Copies the filtered <code>jetspeed.properties</code> portal configuration to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ <br></br>
+ <br></br>
+ As default, the above target folder is configured under the default maven war target folder. The maven
+ <code>clear</code> goal will also remove this filtered <code>jetspeed.properties</code> file.
+ </td></tr><tr class="b"><td><code>j2:portal.conf.tomcat</code></td><td>
+ Copies a filtered Tomcat context descriptor, containing current database connection configuration to the
+ <code>${org.apache.jetspeed.portal.conf.dir}</code> folder.
+ <br></br>
+ <br></br>
+ Based on the <code>${org.apache.jetspeed.catalina.major.version}</code> setting, a Tomcat 5.0.x or 5.5.x
+ type template context descriptor will be used.
+ <br></br>
+ <br></br>
+ The filtered Tomcat context descriptor will be copied to the Tomcat server by the
+ <code>j2:portal.deploy</code> goal.
+ <br></br>
+ <br></br>
+ If you need to change the Tomcat major version and/or database connection configuration, you need to
+ run this goal again before (re)deploying your portal.
+ <br></br>
+ <br></br>
+ As default, the above target folder is configured under the default maven target folder. The maven
+ <code>clear</code> goal will remove this filtered context descriptor file.
+ </td></tr></table></div></div><div class="section"><a name="Portal_Application_Deployment_Goals"></a><h2>Portal Application Deployment Goals</h2><div class="subsection"><a name="Quickstart_deployment_goals"></a><h3>Quickstart deployment goals</h3><p>
+ Several goals are available for quickly deploying the Portal Application together with a predefined set of
+ Portlet Applications and optionally with creating and seeding the portal database.
+ </p><table class="bodyTable"><tr class="a"><th>Goal</th><th>Description</th></tr><tr class="b"><td><code>j2:doStart</code></td><td>
+ A generic goal for deploying the portal application and setting up the required dependencies for the
+ configured Tomcat Server (shared libraries, portal application context, etc.).
+ <br></br>
+ <br></br>
+ This goal requires the plugin property <code>deployType</code> to be set. The default value is
+ <code>"j2:fullDeploy"</code> (see below).
+ <br></br>
+ <br></br>
+ If plugin property <code>recreateDB</code> is set, goal <code>j2:db.recreate</code> is invoked.
+ <br></br>
+ All existing Jetspeed 2 standard and demo portlet applications are removed through goal
+ <code>j2:remove.wars</code>.
+ <br></br>
+ The shared dependecies are copied to the Tomcat Server with goal <code>j2:copy.shared.deps</code>.
+ <br></br>
+ And finally, the set <code>deployType</code> plugin property value is used to run a specific deploy goal.
+ </td></tr><tr class="a"><td><code>j2:quickStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:fullDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td></tr><tr class="b"><td><code>j2:nodbQuickStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbfullDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td></tr><tr class="a"><td><code>j2:basicStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:basicDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td></tr><tr class="b"><td><code>j2:nodbBasicStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbBasicDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td></tr><tr class="a"><td><code>j2:minStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:minDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td></tr><tr class="b"><td><code>j2:nodbMinStart</code></td><td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbMinDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td></tr></table></div><div class="subsection"><a name="Deployment_supporting_Goals"></a><h3>Deployment supporting Goals</h3><table class="bodyTable"><tr class="a"><th>Goal</th><th>Description</th></tr><tr class="b"><td>j2:remove.wars</td><td>
+ Removes the portal, all standard and demo portlet applications (see <code>j2:fullDeploy</code> below)
+ and their context descriptors (if any) from the Tomcat Server.
+ </td></tr><tr class="a"><td><code>j2:catalina.base.shared</code></td><td>
+ Copies all base jars necessary for the common portlet container.
+ </td></tr><tr class="b"><td><code>j2:catalina.shared</code></td><td>Copies all jars necessary for common container</td></tr><tr class="a"><td><code>j2:copy.shared.deps</code></td><td>
+ Wrapper goal invoking <code>j2:catalina.base.shared</code> and <code>j2:catalina.shared</code>.
+ </td></tr><tr class="b"><td><code>j2:portal.deploy</code></td><td>
+ Deploys the portal application only and its dependencies to the Tomcat Server, but no portlet applications.
+ <br></br>
+ <br></br>
+ First, it removes the current portal installation with goal <code>j2:remove.wars</code>.
+ <br></br>
+ Then it copies and expands the build portal war from the local maven repository to the application server.
+ <br></br>
+ And it copies a Tomcat context descriptor for the portal (see also goal <code>j2:portal.conf.tomcat</code>).
+ <br></br>
+ Finally, it installs the shared dependencies with goal <code>j2:copy.shared.deps</code>.
+ </td></tr></table></div><div class="subsection"><a name="Standard_and_Demo_Portlet_Application_deployment_goals"></a><h3>Standard and Demo Portlet Application deployment goals</h3><table class="bodyTable"><tr class="a"><th>Goal</th><th>Description</th></tr><tr class="b"><td><code>j2:deploy</code></td><td>
+ Generic goal to deploy a portlet application identified by property <code>${maven.war.final.name}</code>.
+ <br></br>
+ <br></br>
+ The portlet application is searched for in the Jetspeed2 group of the local maven repository. When
+ searching portlets in the repository, this goal searches for the portlet application given the Jetspeed 2
+ version number configured in the plugin. The name of the file searched in the repository following the
+ convention <code>${maven.war.final.name}-${jetspeed.version}.war</code> and is deployed as
+ <code>${maven.war.final.name}.war</code>.
+ </td></tr><tr class="a"><td><code>j2:pam.layoutdeploy</code></td><td>Deploys Jetspeed local layout portlet application.</td></tr><tr class="b"><td><code>j2:pam.admindeploy</code></td><td>Deploys Jetspeed Administration portlet application.</td></tr><tr class="a"><td><code>j2:pam.tsdeploy</code></td><td>Deploys Pluto Test Suite portlet application.</td></tr><tr class="b"><td><code>j2:pam.strutsdeploy</code></td><td>Deploys the struts mailreader demo portlet application.</td></tr><tr class="a"><td><code>j2:pam.jpetstoredeploy</code></td><td>Deploys the iBatis JPetstore based demo portlet application.</td></tr><tr class="b"><td><code>j2:pam.jsfdeploy</code></td><td>Deploys the JSF demo portlet application which uses Jetspeed generic JSF portlet bridge.</td></tr><tr class="a"><td><code>j2:pam.jsfmyfacesdeploy</code></td><td>Deploys the JSF demo portlet application which uses MyFaces native JSF portlet bridge.</td></tr><tr class="b"><td><code>j2:pam.phpdeploy</code></
td><td>Deploys the Jetspeed PHP bridge demo portlet application.</td></tr><tr class="a"><td><code>j2:pam.perldeploy</code></td><td>Deploys the Jetspeed Perl bridge demo portlet application.</td></tr><tr class="b"><td><code>j2:pam.rssdeploy</code></td><td>Deploys the RSS feed demo portlet application.</td></tr><tr class="a"><td><code>j2:nodbMinDeploy</code></td><td>
+ Deploys the portal using the <code>j2:portal.deploy</code> goal and only the layout and admin portlets
+ using <code>j2:pam.layoutdeploy</code> and <code>j2:pam.admindeploy</code>.
+ </td></tr><tr class="b"><td><code>j2:minDeploy</code></td><td>
+ The same functionality as <code>j2:nodbMinDeploy</code> and additionaly seeds the portal database using
+ the <code>j2:db.entities</code> goal.
+ </td></tr><tr class="a"><td><code>j2:nodbfullDeploy</code></td><td>
+ The same functionality as <code>j2:nodbMinDeploy</code> but additional deploys all other demo portlet
+ applications (see full list above).
+ </td></tr><tr class="b"><td><code>j2:fullDeploy</code></td><td>
+ The same functionality as <code>j2:nodbFullDeploy</code> and additionaly seeds the portal database using
+ the <code>j2:db.entities</code> goal.
+ </td></tr></table></div></div><div class="section"><a name="Database_Management_Goals"></a><h2>Database Management Goals</h2><table class="bodyTable"><tr class="a"><th>Goal</th><th>Description</th></tr><tr class="b"><td><code>j2:start.production.server</code></td><td>Starts a HSQLDB production database for usage by the portal. This goal is optional to those who use the default embedded Derby database.</td></tr><tr class="a"><td><code>j2:start.test.server</code></td><td>
+ Starts a HSQLDB test database to be used for the testcases during the build of Jetspeed 2.
+ This goal is optional for those who use the default embedded Derby database for testing Jetspeed 2.
+ </td></tr><tr class="b"><td><code>j2:db.create.test</code></td><td>
+ Creates the test database tables. If using the HSQLDB database, it should be started first with
+ goal <code>j2:start.test.server</code>.
+ <br></br>
+ Existing portal tables are dropped first. The first time, this will lead to "table does not exist"
+ error messages but they can be (and are) ignored.
+ </td></tr><tr class="a"><td><code>j2:db.create.production</code></td><td>
+ Creates the production database tables. If using the HSQLDB database, it should be started first
+ with goal <code>j2:start.production.server</code>.
+ <br></br>
+ Existing portal tables are dropped first. The first time, this will lead to "table does not exist"
+ kind of error messages but they can (and are) ignored.
+ </td></tr><tr class="b"><td><code>j2:db.recreate</code></td><td>
+ Recreates the production database using the <code>j2:db.create.production</code> goal but first
+ (re)generates the sql scripts using <code>j2:portal.conf.sql</code>.
+ </td></tr><tr class="a"><td><code>j2:db.drop.test</code></td><td>Drops the test database portal tables.</td></tr><tr class="b"><td><code>j2:db.drop.production</code></td><td>Drops the production database portal tables.</td></tr><tr class="a"><td><code>j2:db.entities</code></td><td>
+ Populates the users information for the default PSML configuration configured with Jetspeed 2.
+ </td></tr></table></div><div class="section"><a name="LDAP_Management_Goals"></a><h2>LDAP Management Goals</h2><table class="bodyTable"><tr class="b"><th>Goal</th><th>Description</th></tr><tr class="a"><td><code>j2:start.ldap.server</code></td><td>Starts the default Apache Directory Server and load the default
+ <i><a href="http://svn.apache.org/viewcvs.cgi/portals/jetspeed-2/trunk/etc/apacheds/apacheds-server.xml?view=markup" class="externalLink" title="External Link">apacheds-server.xml</a></i> configuration.</td></tr></table></div><div class="section"><a name="Auxillary_Jetspeed_Components_Deployment_Goals"></a><h2>Auxillary Jetspeed Components Deployment Goals</h2><p>
+ Generic set of goals for redeploying a specific Jetspeed component.
+ </p><table class="bodyTable"><tr class="b"><th>Goal</th><th>Description</th></tr><tr class="a"><td><code>j2:jar.deploy</code></td><td>
+ Deploys a Jetspeed core component from the local maven repository to the deployment directory.
+ </td></tr><tr class="b"><td><code>j2:jar.deploy.shared</code></td><td>
+ Deploys a Jetspeed core component shared library from the local maven repository to the Tomcat shared
+ library directory.
+ </td></tr><tr class="a"><td><code>j2:deployDecorations</code></td><td>
+ Deploys all decoration files from the WEB-INF/decorations directory to the deployed portal.
+ </td></tr><tr class="b"><td><code>j2:deployTemplates</code></td><td>
+ Deploys all template files from the WEB-INF/templates directory to the deployed portal.
+ </td></tr></table></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 1999-2009, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Propchange: portals/site-live/jetspeed-2.1.3/devguide/m2-build/j2-maven-plugin.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-build.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-build.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-build.html (added)
+++ portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-build.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,173 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Jetspeed 2 Enterprise Portal -
+ Building Jetspeed 2.1.x from Source with Maven-2
+ </title><style type="text/css" media="all">
+ @import url("../../style/maven-base.css");
+
+ @import url("../../style/maven-j2.css");@import url("../../style/project.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://portals.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://portals.apache.org/images/apache-portals.gif"></img></a><a href="http://portals.apache.org/jetspeed-2" id="projectLogo"><img alt="Jetspeed 2 Enterprise Portal" src="http://portals.apache.org/images/Jetspeed_blue_med.png"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+ Last published: 23 April 2009
+ | Doc for 2.1.3</div><div class="xright">
+
+ <a href="../../usersguide/index.html">Users Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../adminguide/index.html">Admin Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../deployguide/index.html">Deployers Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../devguide/index.html">Developers Guide</a>
+ </div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuEssentials"><h5>Essentials</h5><ul><li class="none"><a href="../../index.html">Welcome</a></li><li class="none"><a href="../../features.html">Features</a></li><li class="none"><a href="../../getting-started.html">Getting Started</a></li><li class="none"><a href="../../demo.html">Jetspeed Online Demos</a></li></ul></div><div id="menuGet_Jetspeed-2_1_3"><h5>Get Jetspeed-2.1.3</h5><ul><li class="none"><a href="../../download.html">Download</a></li><li class="none"><a href="../../getting-started-installer.html">Installer Instructions</a></li><li class="none"><a href="../../release-notes.html">Release Notes</a></li></ul></div><div id="menuDocumentation_Guides"><h5>Documentation Guides</h5><ul><li class="none"><a href="../../usersguide/index.html">Users Guide</a></li><li class="none"><a href="../../adminguide/index.html">Administrators Guide</a></li><li class="none"><a href=".
./../deployguide/index.html">Deployment Guide</a></li><li class="none"><a href="../../devguide/index.html">Developers Guide</a></li><li class="none"><a href="../../guide-migration.html">Migration Guide</a></li></ul></div><div id="menuAPIs"><h5>APIs</h5><ul><li class="none"><a href="../../multiproject/jetspeed-api/apidocs/index.html">Jetspeed-2 Java API</a></li><li class="none"><a href="../../devguide/guide-ajax-api.html">Jetspeed-2 AJAX API</a></li><li class="none"><a href="../../devguide/j2-maven-plugin.html">Jetspeed-2 Maven-2 Plugin</a></li></ul></div><div id="menuTutorials"><h5>Tutorials</h5><ul><li class="none"><a href="../../tutorials/maven-2/index.html">Jetspeed Tutorial - Maven-2 Custom Build</a></li><li class="none"><a href="../../tutorials/ant/index.html">Jetspeed Tutorial - Ant Custom Build (incomplete)</a></li><li class="none"><a href="../../tutorials/stepbystep/guide-building-custom-portal-maven1.html">Maven-1 Custom Build</a></li><li class="none"><a href="../..
/tutorials/stepbystep/guide-building-custom-portal-maven2.html">Maven-2 Custom Build</a></li></ul></div><div id="menuAbout_Jetspeed-2"><h5>About Jetspeed-2</h5><ul><li class="none"><a href="../../j1-users.html">For Jetspeed-1 Users</a></li><li class="none"><a href="../../j1-migration.html">Jetspeed-1 Migration Guideline</a></li><li class="none"><a href="../../supporting-projects.html">Supporting Projects</a></li><li class="none"><a href="../../who-uses-j2.html">Who Uses J2?</a></li><li class="none"><a href="../../portlets-community.html">Portlets Community</a></li><li class="none"><a href="../../how-to-help.html">How to Help?</a></li></ul></div><div id="menuSupport"><h5>Support</h5><ul><li class="none"><a href="../../mail-lists.html">Mailing List</a></li><li class="none"><a href="../../issue-tracking.html">Bug Database</a></li><li class="none"><a href="http://wiki.apache.org/portals/Jetspeed2" class="externalLink" title="External Link">Wiki</a></li><li class="none"><a href="
../../faq.html">FAQ</a></li></ul></div><div id="menuTranslation"><h5>Translation</h5><ul><li class="none"><a href="http://jetspeed-japan.sourceforge.jp/jetspeed-2-trans/ja/index.html" class="externalLink" title="External Link">Japanese</a></li></ul></div><div id="menuProject_Documentation"><h5>Project Documentation</h5><ul><li class="none"><a href="../../index.html">About Jetspeed 2 Enterprise Portal</a></li><li class="collapsed"><a href="../../project-info.html">Project Info</a></li><li class="collapsed"><a href="../../maven-reports.html">Project Reports</a></li><li class="none"><a href="http://maven.apache.org/development-process.html" class="externalLink" title="External Link">Development Process</a></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="Building_Jetspeed_2_1
_x_from_Source_with_Maven-2"></a><h2>Building Jetspeed 2.1.x from Source with Maven-2</h2><div class="subsection"><a name="Overview"></a><h3>Overview</h3><p>
+ The Maven2 build support is currently under development and is co-resident with the existing Maven1 build scripts and sources.
+ The general strategy is to make heavy use of Ant from within the Maven2 build or as Ant Tasks/Ant Maven2 Plugins if required.
+ For this reason, the Maven2 build can be found in the pom.xml and build.xml files throughout the Jetspeed2 source tree.
+ As with the Maven1 build, it is a multi-module build, primarily following the J2 component and application subprojects.
+ There are also two Maven2 build specific top level subprojects: ant-tasks and maven-archetypes.
+ </p><p>
+ The development team is actively keeping both environments up to date,
+ but the Maven2 build modifications may lag behind newly committed changes.
+ At the moment, Maven2 does not build all LDAP related artifacts and it does not build the uberjar/classworlds executable jar files
+ for the deploy tool. Otherwise it is generally complete, (at least AFAIK).
+ </p><p>
+ Maven 2.0.4 and the accompanying Ant artifact tasks are now being used for this effort,
+ with an upgraded surefire plugin version, (2.1.3). If you wish to use the Maven2 build,
+ please ensure that maven 2.0.4 is installed and in your path.
+ Due to modifications in the pom.xml files, earlier versions of maven will not work correctly.
+ </p></div><div class="subsection"><a name="Future_Directions:_2_2"></a><h3>Future Directions: 2.2</h3><p>This Maven2 build will be deprecated in 2.2, and replaced with a new Maven2 build.
+ The Maven1 build will be completely dropped in 2.2
+ </p></div><div class="subsection"><a name="The_first_step_in_using_Maven2"></a><h3>The first step in using Maven2</h3><p>The first step in using the Maven2 build is to either:
+ <ul>
+ <li>copy the settings.xml.sample to ~/.m2/settings.xml</li>
+ <li>--or--</li>
+ <li>encorporate the settings in this file into your existing Maven2 configuration.</li>
+ </ul>
+ </p></div><div class="subsection"><a name="Properties_Customization"></a><h3>Properties Customization</h3><p>
+ Once in place, please customize the properties as one would have done for Maven1 using build.properties.
+ The properties are preconfigured for embedded Derby, so more changes are required if another database solution is to be used.
+ To complete this step, ensure that the proper jetspeed database active profile is uncommented for your database in
+ the <activeProfiles> element <b>jetspeed-db-drivers-path</b> should be selected for all non-embedded databases.
+ This setting is needed to execute Jetspeed component tests.
+ </p></div><div class="subsection"><a name="Repository_Relocation"></a><h3>Repository Relocation</h3><p>
+While the default location of the settings.xml file should not be changed, (e.g. ~/.m2/settings.xml),
+one can relocate the repository using the <localRepository> element in the settings.xml file.
+See the settings.xml.sample file for an example.
+Note that the repository path must be an absolute path and not contain any property expressions.
+ </p></div><div class="subsection"><a name="Overview_of_current_Jetspeed2_Maven2_commands"></a><h3>Overview of current Jetspeed2 Maven2 commands</h3><p>
+ Here is a quick summary of the current Jetspeed2 Maven2 build commands,
+ (most of these commands can be executed at the root of the J2 source tree or at lower levels to perform partial builds/deployments):
+ </p><table class="bodyTable"><tbody><tr class="a"><td>
+<p> <strong><tt>commands</tt></strong> </p>
+</td><td>
+
+<p> <strong><tt>explanation</tt></strong> </p>
+</td></tr>
+<tr class="b"><td>
+<p> <strong><tt>mvn</tt></strong> </p>
+</td><td>
+<p> performs base build and installs J2 artifacts in the Maven2 repository, (install is the default Maven2 goal for this build)</p>
+
+</td></tr>
+<tr class="a"><td>
+<p> <strong><tt>mvn -P test</tt></strong> </p>
+</td><td>
+<p> performs base build and includes execution of test cases, (includes test database setup) </p>
+</td></tr>
+
+<tr class="b"><td>
+<p> <strong><tt>mvn -P tomcat</tt></strong> </p>
+</td><td>
+<p> performs base build and deploys to Tomcat app server, (includes prodution database setup). Other app servers will be supported in the future, (see below for details)</p>
+</td></tr>
+<tr class="a"><td>
+
+<p> <strong><tt>mvn clean</tt></strong> </p>
+</td><td>
+<p> cleans all build target directories </p>
+</td></tr>
+<tr class="b"><td>
+<p> <strong><tt>other commands</tt></strong> </p>
+
+</td><td>
+<p> explanation </p>
+</td></tr>
+</tbody></table><p><i>Please note that the Maven2 repositories used by default with this build are generally saturated and the Jetspeed2 Maven2
+repository does not yet contain a full mirror of the artifacts required to build Jetspeed2. If you experience download or connection failures,
+ simply restart the build by issuing your last command again to retry.
+ </i></p></div><div class="subsection"><a name="Additional_Notes"></a><h3>Additional Notes</h3><ul>
+ <li><b>mvn -P test</b> and <b>mvn -Dmaven.test.skip=false</b> are equivalent.</li>
+ <li><b>mvn -P test -Dtest=MyTest</b> will execute a single test or matching tests if Ant wildcards are used. </li>
+ <li>Due to forking bugs in the Surefire Maven2 test runner plugin, test output, (e.g. System.out.println()), is not echoed to the build shell. If you wish to see console output for component tests, temporarily comment out the <forkMode>
+ elements in the components/pom.xml and the components pom.xml and run single tests. Note: the forking is required to run multiple tests.
+ </li>
+ <li><p> The <strong><tt>-o</tt></strong> offline option can be specified with the commands documented here to force Maven2 to use only the local repository. This can be invaluable in the event the main Maven2 repositories are down and the build insists upon validating a missing or troublesome POM. </p>
+ </li>
+ </ul><p>
+ </p></div></div><div class="section"><a name="Maven_Profiles"></a><h2>Maven Profiles</h2><p>the following profiles are optional and can be supplied when building/deploying to Tomcat </p><div>
+<table class="bodyTable"><tbody><tr class="a"><td>
+<p> <strong><tt>mvn -P tomcat,min</tt></strong> </p>
+</td><td>
+<p> specified that only the administrative portlets be deployed along with a minimal set of PSML pages.</p>
+</td></tr>
+<tr class="b"><td>
+
+<p> <strong><tt>mvn -P tomcat,full</tt></strong> </p>
+</td><td>
+<p> at the moment, this is the same as the default build: deploys a full J2 set of portlets and PSML pages.</p>
+</td></tr>
+<tr class="a"><td>
+<p> <strong><tt>mvn -P tomcat,nodb</tt></strong> </p>
+
+</td><td>
+<p> specifies that configuration of the production database should be skipped.</p>
+</td></tr>
+<tr class="b"><td>
+<p> <strong><tt>mvn -P tomcat,hot</tt></strong> </p>
+</td><td>
+
+<p> indicates that a portlet app, component, or content should be directly written to the deployed Jetspeed2 webapp.</p>
+</td></tr>
+<tr class="a"><td>
+<p> <strong><tt>mvn -P tomcat,dbpsml</tt></strong> </p>
+</td><td>
+<p> specifies portal build and database deployment/import to include configuration of database PSML.</p>
+
+</td></tr>
+<tr class="b"><td>
+<p> <strong><tt>mvn -P prod</tt></strong> </p>
+</td><td>
+<p> executes deployment to application server specified in settings.xml, (see below).</p>
+</td></tr>
+
+</tbody></table>
+</div><p>Currently, only Tomcat 5 and Tomcat 5.5 application servers are supported by this build. More platforms are to be supported in the near future. To do so, additional deployment profiles and new app-servers Ant deployment build files will need to be added. See the following files for details: </p><ul>
+<li><p> <tt>pom.xml</tt>, </p>
+</li>
+<li><p> <tt>app-servers/tomcat-build.xml</tt>, </p>
+</li>
+<li><p> <tt>maven-archetypes/portal/src/archetype/archetype-resources/pom.xml</tt>, and </p>
+
+</li>
+<li><p> <tt>maven-archetypes/portal/src/archetype/archetype-resources/app-servers/tomcat-build.xml</tt>. </p>
+</li>
+</ul><div class="subsection"><a name="Use_case_for_some_additional_profiles:"></a><h3>Use case for some additional profiles:</h3><p>Some of the additional profiles make sense to preconfigure in your settings.xml, (see the settings.xml.sample file for syntax) </p><ul>
+<li><p> <tt>org.apache.jetspeed.env.deploy.target</tt>, application server to deploy to. Setting this property allows one to use the generic <strong><tt>prod</tt></strong> profile. </p>
+
+</li>
+<li><p> <tt>org.apache.jetspeed.env.deploy.type</tt>, set to <tt>full</tt> or <tt>min</tt>. Takes the place of the <strong><tt>full</tt></strong> and <strong><tt>min</tt></strong> profiles. </p>
+</li>
+
+<li><p> <tt>org.apache.jetspeed.env.deploy.db.psml</tt>, set to <tt>true</tt> or <tt>false</tt>. Equivalent to using <strong><tt>dbpsml</tt></strong> if enabled. </p>
+</li>
+</ul></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 1999-2009, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Propchange: portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-build.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-custom.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-custom.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-custom.html (added)
+++ portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-custom.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,224 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title>Jetspeed 2 Enterprise Portal -
+ Building a Custom Jetspeed 2.1.x Project with Maven-2
+ </title><style type="text/css" media="all">
+ @import url("../../style/maven-base.css");
+
+ @import url("../../style/maven-j2.css");@import url("../../style/project.css");</style><link rel="stylesheet" href="../../style/print.css" type="text/css" media="print"></link><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"></meta></head><body class="composite"><div id="banner"><a href="http://portals.apache.org/" id="organizationLogo"><img alt="Apache Software Foundation" src="http://portals.apache.org/images/apache-portals.gif"></img></a><a href="http://portals.apache.org/jetspeed-2" id="projectLogo"><img alt="Jetspeed 2 Enterprise Portal" src="http://portals.apache.org/images/Jetspeed_blue_med.png"></img></a><div class="clear"><hr></hr></div></div><div id="breadcrumbs"><div class="xleft">
+ Last published: 23 April 2009
+ | Doc for 2.1.3</div><div class="xright">
+
+ <a href="../../usersguide/index.html">Users Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../adminguide/index.html">Admin Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../deployguide/index.html">Deployers Guide</a>
+
+
+
+ <span class="separator">|</span>
+
+
+ <a href="../../devguide/index.html">Developers Guide</a>
+ </div><div class="clear"><hr></hr></div></div><div id="leftColumn"><div id="navcolumn"><div id="menuEssentials"><h5>Essentials</h5><ul><li class="none"><a href="../../index.html">Welcome</a></li><li class="none"><a href="../../features.html">Features</a></li><li class="none"><a href="../../getting-started.html">Getting Started</a></li><li class="none"><a href="../../demo.html">Jetspeed Online Demos</a></li></ul></div><div id="menuGet_Jetspeed-2_1_3"><h5>Get Jetspeed-2.1.3</h5><ul><li class="none"><a href="../../download.html">Download</a></li><li class="none"><a href="../../getting-started-installer.html">Installer Instructions</a></li><li class="none"><a href="../../release-notes.html">Release Notes</a></li></ul></div><div id="menuDocumentation_Guides"><h5>Documentation Guides</h5><ul><li class="none"><a href="../../usersguide/index.html">Users Guide</a></li><li class="none"><a href="../../adminguide/index.html">Administrators Guide</a></li><li class="none"><a href=".
./../deployguide/index.html">Deployment Guide</a></li><li class="none"><a href="../../devguide/index.html">Developers Guide</a></li><li class="none"><a href="../../guide-migration.html">Migration Guide</a></li></ul></div><div id="menuAPIs"><h5>APIs</h5><ul><li class="none"><a href="../../multiproject/jetspeed-api/apidocs/index.html">Jetspeed-2 Java API</a></li><li class="none"><a href="../../devguide/guide-ajax-api.html">Jetspeed-2 AJAX API</a></li><li class="none"><a href="../../devguide/j2-maven-plugin.html">Jetspeed-2 Maven-2 Plugin</a></li></ul></div><div id="menuTutorials"><h5>Tutorials</h5><ul><li class="none"><a href="../../tutorials/maven-2/index.html">Jetspeed Tutorial - Maven-2 Custom Build</a></li><li class="none"><a href="../../tutorials/ant/index.html">Jetspeed Tutorial - Ant Custom Build (incomplete)</a></li><li class="none"><a href="../../tutorials/stepbystep/guide-building-custom-portal-maven1.html">Maven-1 Custom Build</a></li><li class="none"><a href="../..
/tutorials/stepbystep/guide-building-custom-portal-maven2.html">Maven-2 Custom Build</a></li></ul></div><div id="menuAbout_Jetspeed-2"><h5>About Jetspeed-2</h5><ul><li class="none"><a href="../../j1-users.html">For Jetspeed-1 Users</a></li><li class="none"><a href="../../j1-migration.html">Jetspeed-1 Migration Guideline</a></li><li class="none"><a href="../../supporting-projects.html">Supporting Projects</a></li><li class="none"><a href="../../who-uses-j2.html">Who Uses J2?</a></li><li class="none"><a href="../../portlets-community.html">Portlets Community</a></li><li class="none"><a href="../../how-to-help.html">How to Help?</a></li></ul></div><div id="menuSupport"><h5>Support</h5><ul><li class="none"><a href="../../mail-lists.html">Mailing List</a></li><li class="none"><a href="../../issue-tracking.html">Bug Database</a></li><li class="none"><a href="http://wiki.apache.org/portals/Jetspeed2" class="externalLink" title="External Link">Wiki</a></li><li class="none"><a href="
../../faq.html">FAQ</a></li></ul></div><div id="menuTranslation"><h5>Translation</h5><ul><li class="none"><a href="http://jetspeed-japan.sourceforge.jp/jetspeed-2-trans/ja/index.html" class="externalLink" title="External Link">Japanese</a></li></ul></div><div id="menuProject_Documentation"><h5>Project Documentation</h5><ul><li class="none"><a href="../../index.html">About Jetspeed 2 Enterprise Portal</a></li><li class="collapsed"><a href="../../project-info.html">Project Info</a></li><li class="collapsed"><a href="../../maven-reports.html">Project Reports</a></li><li class="none"><a href="http://maven.apache.org/development-process.html" class="externalLink" title="External Link">Development Process</a></li></ul></div><a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy"><img alt="Built by Maven" src="../../images/logos/maven-button-1.png"></img></a></div></div><div id="bodyColumn"><div class="contentBox"><div class="section"><a name="How-to_for_Building_a
_Custom_Portal_with_Maven-2_and_Jetspeed_2_1_x"></a><h2>How-to for Building a Custom Portal with Maven-2 and Jetspeed 2.1.x</h2><div class="subsection"><a name="Custom_Portal_Generation"></a><h3>Custom Portal Generation</h3><p>
+The Maven1 j2:portal.genapp goal has been supported in the Maven2 build as an archetype.
+ However, until a Jetspeed2 Maven2 repository is completely populated, a normal Maven2 build must be completed to make Jetspeed2 archetypes
+ available in your local repository. One can tweak the following command as needed to create a Jetspeed2 instance using this archetype:
+ </p><p><b>
+ mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2 -DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1.3 -DgroupId=myportalgroup -DartifactId=myportal -Dversion=1.0
+ </b>
+ </p></div><div class="subsection"><a name="Custom_Portal_Directory_Structure_Conventions"></a><h3>Custom Portal Directory Structure Conventions</h3><p>
+Note that this and other archetypes can issue many harmless warnings while expanding.
+Please ignore the warnings unless the expansion of the archetype template fails. When complete, the portal archetype expansion will contain the following structure
+ within a directory named as the specified artifactId relative to the current working directory:
+ </p><ul>
+<li><p><tt><artifactId>/applications</tt> - conventional subdirectory for portal application war modules. </p>
+</li>
+<li><p> <tt><artifactId>/app-servers</tt> - contains portal deployment builds and resources. </p>
+</li>
+<li><p> <tt><artifactId>/components</tt> - conventional subdirectory for portal component jar modules. </p>
+</li>
+<li><p> <tt><artifactId>/etc/assembly</tt> - custom portal application component Spring assemblies. </p>
+
+</li>
+<li><p> <tt><artifactId>/etc/conf</tt> - portal application context configuration files. </p>
+</li>
+<li><p> <tt><artifactId>/etc/decorations</tt> - custom decorations in images, layout, and portlet subdirectories. </p>
+</li>
+<li><p> <tt><artifactId>/etc/pages</tt> - custom portal PSML pages to augment/override minimal defaults, (e.g. /Administrative/**, /default-page.psml, /myaccount.psml, /page.security, and /system/**). </p>
+
+</li>
+<li><p> <tt><artifactId>/etc/schema</tt> - Jetspeed2 database schema definitions. </p>
+</li>
+<li><p> <tt><artifactId>/etc/sql</tt> - Jetspeed2 base database configuration scripts. </p>
+</li>
+<li><p> <tt><artifactId>/etc/templates</tt> - custom overrides for Jetspeed2 layout portlet templates. </p>
+
+</li>
+<li><p> <tt><artifactId>/etc/webapp</tt> - custom content reaources to be packaged with portal application. </p>
+</li>
+<li><p> <tt><artifactId>/portal</tt> - portal application war build scripts and webapp resource overrides. </p>
+</li>
+<li><p> <tt><artifactId>/src</tt> - these directories are an artifact of archetype expansion and should be deleted. </p>
+
+</li>
+</ul></div><div class="subsection"><a name="Configuration"></a><h3>Configuration</h3><p>The archetype also contains a settings.xml.sample that is a subset of the Jetspeed2 source build parameters.
+If one has not previously configured the ~/.m2/settings.xml file as described above, this sample can be used to do so without J2 test configurations. </p><p>When the Maven2 enviroment is properly configured, the J2 Maven2 commands outlined above can now be used to build and deploy a customized portal.
+ Most of the command options are supported with the exception of these profiles: </p><ul>
+<li><p> <strong><tt>min</tt></strong> and <strong><tt>full</tt></strong> are not supported because the archetype supports only the minimal deployment. </p>
+</li>
+<li><p> <strong><tt>test</tt></strong> features to populate the J2 test database have also been provisionally stripped from the archetype. </p>
+</li>
+<li><p> <strong><tt>dbpsml</tt></strong> is not yet supported in the custom portal build to import to the production database PSML. </p>
+</li>
+</ul><p>Currently, only Maven2 builds are supported. Longer range goals include support for Ant custom portal builds and prepackaged Maven2 repository downloads. </p><p>Two additional Maven2 archetypes are also available to generate custom portal applications and components on top of the generated portal template. Before these archetypes are used, the host portal archetype should have been previously built to install all parent POMs, (it is not necessary to deploy the portal before using these archetypes). These archetypes should be created from the applications and components subdirectories to work correctly. </p></div><div class="subsection"><a name="Archetype_Commands"></a><h3>Archetype Commands</h3><p>A portal portlets application to be deployed by Jetspeed2: </p><p><strong><tt>mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2 -DarchetypeArtifactId=application-archetype -DarchetypeVersion=2.1.3 -DgroupId=myportalgroup -DartifactId=myportal-application
-Dversion=1.0</tt></strong> </p><p>A simple component to be used by other component and application modules: </p><p><strong><tt>mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2 -DarchetypeArtifactId=component-archetype -DarchetypeVersion=2.1.3 -DgroupId=myportalgroup -DartifactId=myportal-component -Dversion=1.0</tt></strong> </p><p>A shared component to be deployed as a shared JAR in the application server: </p><p><strong><tt>mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2 -DarchetypeArtifactId=shared-component-archetype -DarchetypeVersion=2.1.3 -DgroupId=myportalgroup -DartifactId=myportal-shared-component -Dversion=1.0</tt></strong> </p><p>A component to be deployed within the portal, (Jetspeed2), web application: </p><p><strong><tt>mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2 -DarchetypeArtifactId=portal-component-archetype -DarchetypeVersion=2.1.3 -DgroupId=myportalgroup -DartifactId=myportal-portal-co
mponent -Dversion=1.0</tt></strong> </p><p><em>Note that the groupId and version settings should match the values used when generating the host portal template.</em> </p></div><div class="subsection"><a name="Maven_POM_Configuration"></a><h3>Maven POM Configuration</h3><p>There are a few manual steps that must be followed to use these created applications and components. </p><ul>
+<li><p>The new application/component must be added as <module> elements in the parent POM. An application would be added like this by subdirectory name, (artifactId):
+</p>
+<pre><modules>
+ ...
+ <module>myportal-application</module>
+
+ ...
+</modules>
+</pre>
+<p>The same syntax is used for components.</p>
+</li>
+<li class="gap"><p>A dependency declaration should be added in the root POM. Components packaged as jars should be added like this:
+</p>
+<pre><dependencyManagement>
+ <dependencies>
+ ...
+ <dependency>
+
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>myportal-component</artifactId>
+ <version>${pom.version}</version>
+ </dependency>
+
+ ...
+ </dependencies>
+</dependencyManagement>
+</pre>
+<p>Applications are declared similarly, except for the addition of a required <type> element:
+</p>
+<pre><dependencyManagement>
+ <dependencies>
+
+ ...
+ <dependency>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>myportal-application</artifactId>
+ <type>war</type>
+
+ <version>${pom.version}</version>
+ </dependency>
+ ...
+ </dependencies>
+</dependencyManagement>
+</pre>
+</li>
+<li class="gap"><p>These dependencies can now be used to include the applications and components into the build process. Components are added as included dependencies to other applications and components in individual POMs associated with the modules that reference the component:
+
+</p>
+<pre><dependencies>
+ ...
+ <dependency>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>myportal-component</artifactId>
+
+ </dependency>
+ ...
+</dependencies>
+</pre>
+<p>Shared components that are intended to be deployed as a shared JAR should be declared as a provided dependency in the applications POM or individual application and component POMs, (note the additional provided <scope> element):
+</p>
+<pre><dependencies>
+ ...
+ <dependency>
+
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>myportal-shared-component</artifactId>
+ <scope>provided</scope>
+ </dependency>
+
+ ...
+</dependencies>
+</pre>
+<p>Shared and portal components must also be made available for deployment and should be integrated in the app-servers module POM as a normal dependency:
+</p>
+<pre><dependencies>
+ ...
+ <dependency>
+ <groupId>${pom.groupId}</groupId>
+
+ <artifactId>myportal-shared-component</artifactId>
+ </dependency>
+ ...
+</dependencies>
+</pre>
+<p>Applications are normally referenced only for deployment. To ensure they are available during deployment builds, they must be integrated in the app-servers module POM like this:
+</p>
+<pre><dependencies>
+
+ ...
+ <dependency>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>myportal-application</artifactId>
+ <type>war</type>
+
+ </dependency>
+ ...
+</dependencies>
+</pre>
+</li>
+<li class="gap"><p>Finally, the new applications and components must be added to the app-servers deployment Ant buildfiles. Applications should be added to the 'hot' application/WAR deployment hooks in the application server specific build files, (e.g. tomcat-build.xml):
+</p>
+<pre><target name="hot-deploy-apps">
+ ...
+ <antcall target="hot-deploy-war">
+
+ <param name="org.apache.jetspeed.deploy.groupid" value="${portal.groupid}"/>
+ <param name="org.apache.jetspeed.deploy.artifactid" value="myportal-application"/>
+ <param name="org.apache.jetspeed.deploy.version" value="${portal.version}"/>
+ </antcall>
+ ...
+</target>
+</pre>
+
+<p>Shared components that are to be installed in the application server should be added to the shared deployment hook in the same buildfile:
+</p>
+<pre><target name="hot-deploy-shared-components">
+ ...
+ <antcall target="hot-deploy-shared-jar">
+ <param name="org.apache.jetspeed.deploy.groupid" value="${portal.groupid}"/>
+ <param name="org.apache.jetspeed.deploy.artifactid" value="myportal-shared-component"/>
+ <param name="org.apache.jetspeed.deploy.version" value="${portal.version}"/>
+
+ </antcall>
+ ...
+</target>
+</pre>
+<p>And finally, portal components that are to be inserted into the portal application itself should be added to the 'hot' component/JAR hooks like this:
+</p>
+<pre><target name="hot-deploy-components">
+ ...
+ <antcall target="hot-deploy-jar">
+ <param name="org.apache.jetspeed.deploy.groupid" value="${portal.groupid}"/>
+
+ <param name="org.apache.jetspeed.deploy.artifactid" value="myportal-portal-component"/>
+ <param name="org.apache.jetspeed.deploy.version" value="${portal.version}"/>
+ </antcall>
+ ...
+</target>
+</pre>
+</li>
+</ul><p>Please refer to the Maven2 site documentation for more detail or background information: <a href="http://maven.apache.org/guides/index.html" class="externalLink" title="External Link">Maven-2 Docs</a></p></div></div></div></div><div class="clear"><hr></hr></div><div id="footer"><div class="xright">© 1999-2009, Apache Software Foundation</div><div class="clear"><hr></hr></div></div></body></html>
\ No newline at end of file
Propchange: portals/site-live/jetspeed-2.1.3/devguide/m2-build/maven-2-custom.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/devguide/maven-2-build.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/devguide/maven-2-build.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/devguide/maven-2-build.html (added)
+++ portals/site-live/jetspeed-2.1.3/devguide/maven-2-build.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,393 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed 2 -
+ Building Jetspeed 2.1.x from Source with Maven-2
+ </title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Essentials</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Welcome</a>
+ </li>
+
+ <li class="none">
+ <a href="features.html">Features</a>
+ </li>
+
+ <li class="none">
+ <a href="getting-started.html">Getting Started</a>
+ </li>
+
+ <li class="none">
+ <a href="demo.html">Jetspeed Online Demos</a>
+ </li>
+ </ul>
+ <h5>Get Jetspeed</h5>
+ <ul>
+
+ <li class="none">
+ <a href="download.html">Download</a>
+ </li>
+
+ <li class="none">
+ <a href="getting-started-installer.html">Installer Instructions</a>
+ </li>
+
+ <li class="none">
+ <a href="release-notes.html">Release Notes</a>
+ </li>
+ </ul>
+ <h5>Documentation Guides</h5>
+ <ul>
+
+ <li class="none">
+ <a href="usersguide/index.html">Users Guide</a>
+ </li>
+
+ <li class="none">
+ <a href="adminguide/index.html">Administrators Guide</a>
+ </li>
+
+ <li class="none">
+ <a href="deployguide/index.html">Deployment Guide</a>
+ </li>
+
+ <li class="none">
+ <a href="devguide/index.html">Developers Guide</a>
+ </li>
+ </ul>
+ <h5>Migration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="guide-migration.html">Migration Guide</a>
+ </li>
+
+ <li class="none">
+ <a href="j1-migration.html">Jetspeed-1 Migration Guideline</a>
+ </li>
+
+ <li class="none">
+ <a href="j1-users.html">For Jetspeed-1 Users</a>
+ </li>
+ </ul>
+ <h5>APIs</h5>
+ <ul>
+
+ <li class="none">
+ <a href="apidocs/jetspeed-api/index.html">Jetspeed-2 Java API</a>
+ </li>
+
+ <li class="none">
+ <a href="devguide/guide-ajax-api.html">Jetspeed-2 AJAX API</a>
+ </li>
+ </ul>
+ <h5>Tutorials</h5>
+ <h5>Community</h5>
+ <ul>
+
+ <li class="none">
+ <a href="supporting-projects.html">Supporting Projects</a>
+ </li>
+
+ <li class="none">
+ <a href="who-uses-j2.html">Who Uses J2?</a>
+ </li>
+
+ <li class="none">
+ <a href="portlets-community.html">Portlets Community</a>
+ </li>
+
+ <li class="none">
+ <a href="how-to-help.html">How to Help?</a>
+ </li>
+ </ul>
+ <h5>Support</h5>
+ <ul>
+
+ <li class="none">
+ <a href="mail-lists.html">Mailing List</a>
+ </li>
+
+ <li class="none">
+ <a href="issue-tracking.html">Bug Database</a>
+ </li>
+
+ <li class="none">
+ <a href="http://wiki.apache.org/portals/Jetspeed2" class="externalLink">Wiki</a>
+ </li>
+
+ <li class="none">
+ <a href="faq.html">FAQ</a>
+ </li>
+ </ul>
+ <h5>Translation</h5>
+ <ul>
+
+ <li class="none">
+ <a href="http://jetspeed-japan.sourceforge.jp/jetspeed-2-trans/ja/index.html" class="externalLink">Japanese</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"></authors><div class="section"><h2><a name="Building_Jetspeed_2.1.x_from_Source_with_Maven-2"></a>Building Jetspeed 2.1.x from Source with Maven-2</h2>
+<div class="section"><h3><a name="Overview"></a>Overview</h3>
+<p>
+ The Maven2 build support is currently under development and is co-resident with the existing Maven1 build scripts and sources.
+ The general strategy is to make heavy use of Ant from within the Maven2 build or as Ant Tasks/Ant Maven2 Plugins if required.
+ For this reason, the Maven2 build can be found in the pom.xml and build.xml files throughout the Jetspeed2 source tree.
+ As with the Maven1 build, it is a multi-module build, primarily following the J2 component and application subprojects.
+ There are also two Maven2 build specific top level subprojects: ant-tasks and maven-archetypes.
+ </p>
+<p>
+ The development team is actively keeping both environments up to date,
+ but the Maven2 build modifications may lag behind newly committed changes.
+ At the moment, Maven2 does not build all LDAP related artifacts and it does not build the uberjar/classworlds executable jar files
+ for the deploy tool. Otherwise it is generally complete, (at least AFAIK).
+ </p>
+<p>
+ Maven 2.0.4 and the accompanying Ant artifact tasks are now being used for this effort,
+ with an upgraded surefire plugin version, (2.1.3). If you wish to use the Maven2 build,
+ please ensure that maven 2.0.4 is installed and in your path.
+ Due to modifications in the pom.xml files, earlier versions of maven will not work correctly.
+ </p>
+</div>
+<div class="section"><h3><a name="Future_Directions:_2.2"></a>Future Directions: 2.2</h3>
+<p>This Maven2 build will be deprecated in 2.2, and replaced with a new Maven2 build.
+ The Maven1 build will be completely dropped in 2.2
+ </p>
+</div>
+<div class="section"><h3><a name="The_first_step_in_using_Maven2"></a>The first step in using Maven2</h3>
+<p>The first step in using the Maven2 build is to either:
+ <ul><li>copy the settings.xml.sample to ~/.m2/settings.xml</li>
+<li>--or--</li>
+<li>encorporate the settings in this file into your existing Maven2 configuration.</li>
+</ul>
+</p>
+</div>
+<div class="section"><h3><a name="Properties_Customization"></a>Properties Customization</h3>
+<p>
+ Once in place, please customize the properties as one would have done for Maven1 using build.properties.
+ The properties are preconfigured for embedded Derby, so more changes are required if another database solution is to be used.
+ To complete this step, ensure that the proper jetspeed database active profile is uncommented for your database in
+ the <activeProfiles> element <b>jetspeed-db-drivers-path</b> should be selected for all non-embedded databases.
+ This setting is needed to execute Jetspeed component tests.
+ </p>
+</div>
+<div class="section"><h3><a name="Repository_Relocation"></a>Repository Relocation</h3>
+<p>
+While the default location of the settings.xml file should not be changed, (e.g. ~/.m2/settings.xml),
+one can relocate the repository using the <localRepository> element in the settings.xml file.
+See the settings.xml.sample file for an example.
+Note that the repository path must be an absolute path and not contain any property expressions.
+ </p>
+</div>
+<div class="section"><h3><a name="Overview_of_current_Jetspeed2_Maven2_commands"></a>Overview of current Jetspeed2 Maven2 commands</h3>
+<p>
+ Here is a quick summary of the current Jetspeed2 Maven2 build commands,
+ (most of these commands can be executed at the root of the J2 source tree or at lower levels to perform partial builds/deployments):
+ </p>
+<table class="bodyTable"><tbody><tr class="a"><td><p><strong><tt>commands</tt></strong></p>
+</td>
+<td><p><strong><tt>explanation</tt></strong></p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>mvn</tt></strong></p>
+</td>
+<td><p> performs base build and installs J2 artifacts in the Maven2 repository, (install is the default Maven2 goal for this build)</p>
+</td>
+</tr>
+<tr class="a"><td><p><strong><tt>mvn -P test</tt></strong></p>
+</td>
+<td><p> performs base build and includes execution of test cases, (includes test database setup) </p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>mvn -P tomcat</tt></strong></p>
+</td>
+<td><p> performs base build and deploys to Tomcat app server, (includes prodution database setup). Other app servers will be supported in the future, (see below for details)</p>
+</td>
+</tr>
+<tr class="a"><td><p><strong><tt>mvn clean</tt></strong></p>
+</td>
+<td><p> cleans all build target directories </p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>other commands</tt></strong></p>
+</td>
+<td><p> explanation </p>
+</td>
+</tr>
+</tbody></table>
+<p><i>Please note that the Maven2 repositories used by default with this build are generally saturated and the Jetspeed2 Maven2
+repository does not yet contain a full mirror of the artifacts required to build Jetspeed2. If you experience download or connection failures,
+ simply restart the build by issuing your last command again to retry.
+ </i></p>
+</div>
+<div class="section"><h3><a name="Additional_Notes"></a>Additional Notes</h3>
+<ul><li><b>mvn -P test</b> and <b>mvn -Dmaven.test.skip=false</b> are equivalent.</li>
+<li><b>mvn -P test -Dtest=MyTest</b> will execute a single test or matching tests if Ant wildcards are used. </li>
+<li>Due to forking bugs in the Surefire Maven2 test runner plugin, test output, (e.g. System.out.println()), is not echoed to the build shell. If you wish to see console output for component tests, temporarily comment out the <forkMode>
+ elements in the components/pom.xml and the components pom.xml and run single tests. Note: the forking is required to run multiple tests.
+ </li>
+<li> The <strong><tt>-o</tt></strong> offline option can be specified with the commands documented here to force Maven2 to use only the local repository. This can be invaluable in the event the main Maven2 repositories are down and the build insists upon validating a missing or troublesome POM. </li>
+</ul>
+<p></p>
+</div>
+</div>
+<div class="section"><h2><a name="Maven_Profiles"></a>Maven Profiles</h2>
+<p>the following profiles are optional and can be supplied when building/deploying to Tomcat </p>
+<div><table class="bodyTable"><tbody><tr class="a"><td><p><strong><tt>mvn -P tomcat,min</tt></strong></p>
+</td>
+<td><p> specified that only the administrative portlets be deployed along with a minimal set of PSML pages.</p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>mvn -P tomcat,full</tt></strong></p>
+</td>
+<td><p> at the moment, this is the same as the default build: deploys a full J2 set of portlets and PSML pages.</p>
+</td>
+</tr>
+<tr class="a"><td><p><strong><tt>mvn -P tomcat,nodb</tt></strong></p>
+</td>
+<td><p> specifies that configuration of the production database should be skipped.</p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>mvn -P tomcat,hot</tt></strong></p>
+</td>
+<td><p> indicates that a portlet app, component, or content should be directly written to the deployed Jetspeed2 webapp.</p>
+</td>
+</tr>
+<tr class="a"><td><p><strong><tt>mvn -P tomcat,dbpsml</tt></strong></p>
+</td>
+<td><p> specifies portal build and database deployment/import to include configuration of database PSML.</p>
+</td>
+</tr>
+<tr class="b"><td><p><strong><tt>mvn -P prod</tt></strong></p>
+</td>
+<td><p> executes deployment to application server specified in settings.xml, (see below).</p>
+</td>
+</tr>
+</tbody></table>
+</div><p>Currently, only Tomcat 5 and Tomcat 5.5 application servers are supported by this build. More platforms are to be supported in the near future. To do so, additional deployment profiles and new app-servers Ant deployment build files will need to be added. See the following files for details: </p>
+<ul><li><tt>pom.xml</tt>, </li>
+<li><tt>app-servers/tomcat-build.xml</tt>, </li>
+<li><tt>maven-archetypes/portal/src/archetype/archetype-resources/pom.xml</tt>, and </li>
+<li><tt>maven-archetypes/portal/src/archetype/archetype-resources/app-servers/tomcat-build.xml</tt>. </li>
+</ul>
+<div class="section"><h3><a name="Use_case_for_some_additional_profiles:"></a>Use case for some additional profiles:</h3>
+<p>Some of the additional profiles make sense to preconfigure in your settings.xml, (see the settings.xml.sample file for syntax) </p>
+<ul><li><tt>org.apache.jetspeed.env.deploy.target</tt>, application server to deploy to. Setting this property allows one to use the generic <strong><tt>prod</tt></strong> profile. </li>
+<li><tt>org.apache.jetspeed.env.deploy.type</tt>, set to <tt>full</tt> or <tt>min</tt>. Takes the place of the <strong><tt>full</tt></strong> and <strong><tt>min</tt></strong> profiles. </li>
+<li><tt>org.apache.jetspeed.env.deploy.db.psml</tt>, set to <tt>true</tt> or <tt>false</tt>. Equivalent to using <strong><tt>dbpsml</tt></strong> if enabled. </li>
+</ul>
+</div>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/devguide/maven-2-build.html
------------------------------------------------------------------------------
svn:executable = *