Log of /portals/pluto/branches/pluto-1.0.2/GETTING-STARTED.html
Parent Directory
|
Revision Log
Revision
35835 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Jan 8 14:33:08 2004 UTC
(5 years, 10 months ago)
by
weaver
Original Path:
portals/pluto/trunk/GETTING-STARTED.html
File length: 3476 byte(s)
Diff to
previous 35827
(
colored)
Added three new sections to GETTING-STARTED.HTML
- What if I just want the Pluto container jar (like for Jetspeed 2)?
- What if I just want to deploy the Pluto portal without the test suite?
- What if I decide I want to deploy the test suite portlets after I deploy the Pluto portal by itself?
Revision
35820 -
(
view)
(
annotate)
-
[select for diffs]
Added
Wed Jan 7 20:37:24 2004 UTC
(5 years, 10 months ago)
by
weaver
Original Path:
portals/pluto/trunk/GETTING-STARTED.html
File length: 2052 byte(s)
Changes made to fully mavenize the Pluto build.
- Re-arranged the source tree into self contained sub projects
- api: the portlet api
- container: the pluto container
- portal: Pluto portal implementation
- testsuite: the portlets test suite
all structures are laid out like this:
src/java - all java source files
src/resources - all non-java classpath resources
src/webapp - webapp war structure
NOTE: some sub-projects may not have all of directories listed above.
- moved the war directory source into portal/src/webapp
- portlets folder is deprecated, the test suite portlets are now
housed entirely under the testsuite sub-project
- we use maven's reactor capability to build and deploy Pluto in one foul swoop
using maven fullDeployment from the project root directory.
Please see the GETTING-STARTED.html on how to go about building
and deploying Pluto with maven.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.