| /[Apache-SVN]/portals/pluto/branches/pluto-1.0.2/project.xml |
Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Moving Trunk to 1.0.2 branch. About to move 1.1 to Trunk
Site update for 1.0.1
First commit: moved myself (Zhong ZHENG) from contributor list to developer list.
Added Ken Atherton as a contributor for his help on the admin portlets.
Beginning the 1.0.1 release. Sorry for the delay.
Changed mail list archives links to mail-archives.apache.org URL
Build Updates: - PLUTO-152: Thanks Jeremy Boynes - Updating Maven Build - Updating 1.0.1-rc4 properties to 1.0.1-SNAPSHOT
Changed url of repository so cvs-usage.html would point to ViewCVS snapshot of SVN repository.
-- Adding Zheng as a contributor to the project. Thanks for all your work on RC4! -- Adding the Chinese translation as a link on the top of every page. -- Updating release status.
Rolling source over to RC4 Updating changes.xml.
updating site deploy location.
compile source to match target 1.3. . .update personal info.
Changed nagoya.apache.org references to issues.apache.org as suggested in PLUTO-127
Added my name (cdoremus) as a developer
Updating versions to RC3 to prepare for release.
Updated version to 1.0.1-rc2
Adding Ken Weiner as a contributor. Thanks for the input and patches.
Correct version
Updating my info.
Update info
Update
Change mailing lists
Updating Pluto Documentation in order to prepare for portals.apache.org release
Use maven deploy mechanism for website again to be inline with the other portals projects
Update version info
Credited Michael Westbay as a contributor for his patches
Adding changes
Update to new license
Removing tab characters which I accidently committed.
Added myself to developers
Adding myself to the developer list. Testing new account/commit karma
Apply patch from David H. DeWolf to use the Maven multi-project feature
Added my name, e-mail address
Make building the site work - we can directly use the "site" goal
o Remove dependencies. Each project.xml must include its own depenencies. o Update ID for developers
root project.xml should not have any dependencies. A dep on portlet-api was causing the /api sub-project to not build
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.
Updated id
Correct dependencies
added my name to the developer list
Adding myself :)
changed version to 1.0
- xdocs now use a "modified" version of the pluto (the planet) logo that has the Apache feather super imposed over it. - included the source .psd photoshop file
Added maven project descriptors, thanks to David DeWolf. I modified David's intial post as follows: - Added the portlet-api depdency to the project - Added an "allDoc" goal that builds both the xdocs and the api docs - Added my info to the developers list - Obfuscated everybody's email addresses to protect them from spam harvestors.
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.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |