You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rave.apache.org by ja...@apache.org on 2012/03/26 20:57:29 UTC
svn commit: r1305493 - in /rave/site/trunk/content/rave: edit-website.mdtext
get-involved.mdtext ide-settings-and-debugging.mdtext index.mdtext
issue-management.mdtext mailing-lists.mdtext source.mdtext
Author: jasha
Date: Mon Mar 26 18:57:29 2012
New Revision: 1305493
URL: http://svn.apache.org/viewvc?rev=1305493&view=rev
Log:
RAVE-527 Rave -> Apache Rave. Update mailing list email addresses (archives still pointing to incubator)
Modified:
rave/site/trunk/content/rave/edit-website.mdtext
rave/site/trunk/content/rave/get-involved.mdtext
rave/site/trunk/content/rave/ide-settings-and-debugging.mdtext
rave/site/trunk/content/rave/index.mdtext
rave/site/trunk/content/rave/issue-management.mdtext
rave/site/trunk/content/rave/mailing-lists.mdtext
rave/site/trunk/content/rave/source.mdtext
Modified: rave/site/trunk/content/rave/edit-website.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/edit-website.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/edit-website.mdtext (original)
+++ rave/site/trunk/content/rave/edit-website.mdtext Mon Mar 26 18:57:29 2012
@@ -31,7 +31,7 @@ HTML pages directly. The actual edit is
(see the commit mail with "Staging update by buildbot" as log messge).
2. Second you need to publish the staging part to the production section (see the
- commit mail with "Publishing merge to rave site by <your Apache ID>"
+ commit mail with "Publishing merge to Apache Rave site by <your Apache ID>"
as log message).
## What do you prefer: Working via command line or in the browser?
Modified: rave/site/trunk/content/rave/get-involved.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/get-involved.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/get-involved.mdtext (original)
+++ rave/site/trunk/content/rave/get-involved.mdtext Mon Mar 26 18:57:29 2012
@@ -87,22 +87,22 @@ to approve a release.
We welcome code contributions for both existing and new project issues. If you wish to contribute a solution to an existing entry in
[Rave's Jira][15], please first comment on the issue to provide a description and patch for your solution. Submitting the patch to
Apache's Jira and selecting the "Grant license to ASF for inclusion" option is required. Then submit your patch to
-the [Apache review system][16] and post a review request to the Rave developer mailing list.
+the [Apache review system][16] and post a review request to the Apache Rave developer mailing list.
If you wish to submit a solution to a problem that has not been identified in Rave's Jira, first create the new issue following our
[guidelines][17] and then submit your patch to the review system as before.
In either case, the easiest way to create a patch on the command line is by running the command ''svn diff > Rave-XYZ.patch'' from
-the top level Rave directory, where XYZ is the Jira issue number.
+the top level Apache Rave directory, where XYZ is the Jira issue number.
- [1]: mailto://rave-dev-subscribe@incubator.apache.org
- [2]: mailto://rave-dev@incubator.apache.org
- [3]: mailto:rave-dev-unsubscribe@incubator.apache.org
+ [1]: mailto:dev-subscribe@rave.apache.org
+ [2]: mailto:dev@rave.apache.org
+ [3]: mailto:dev-unsubscribe@rave.apache.org
[4]: http://markmail.org/search/+list:org.apache.incubator.rave-dev
[5]: http://mail-archives.apache.org/mod_mbox/incubator-rave-dev/
- [6]: mailto:rave-commits-subscribe@incubator.apache.org
- [7]: mailto:rave-commmits-unsubscribe@incubator.apache.org
+ [6]: mailto:commits-subscribe@rave.apache.org
+ [7]: mailto:commmits-unsubscribe@rave.apache.org
[8]: http://markmail.org/search/+list:org.apache.incubator.rave-commits
[9]: http://mail-archives.apache.org/mod_mbox/incubator-rave-commits/
[10]: /rave/docs/governance/lazyConsensus.html
Modified: rave/site/trunk/content/rave/ide-settings-and-debugging.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/ide-settings-and-debugging.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/ide-settings-and-debugging.mdtext (original)
+++ rave/site/trunk/content/rave/ide-settings-and-debugging.mdtext Mon Mar 26 18:57:29 2012
@@ -45,7 +45,7 @@ Notice: Licensed to the Apache Softwa
other).
Now the application is building you probably want to be able to develop and debug
-Rave from inside Eclipse. This gives a faster turnaround in the
+Apache Rave from inside Eclipse. This gives a faster turnaround in the
edit/build/deploy cycle.
There are a few different ways to do this:
@@ -65,7 +65,7 @@ environment under rave-portal/target/Tom
Prerequisite: install the Eclipse FileSync plugin from its [Update Site][8]. You need to select plugin based on eclipse version.
For Eclipse 3.7 select Eclipse 3.5 -3.7 plugins and Eclipse 3.6 -3.7 plugins(Bytecode outline)
-The first time you build the Rave project with maven, the maven-filesync-plugin
+The first time you build the Apache Rave project with maven, the maven-filesync-plugin
will generate this default FileSync configuration for the FileSync plugin.
Afterwards you only have to refresh the Eclipse projects once to have them recognize this.
Thereafter you can customize the synchronization configuration manually within Eclipse through
@@ -78,15 +78,15 @@ changes automatically after you saved th
synchronization from the project (rave-portal or rave-shindig) its context menu actions.
### Using Eclipse WTP
-The Rave project can also be deployed through Eclipse WTP, and might be adequate for some, but it
+The Apache Rave project can also be deployed through Eclipse WTP, and might be adequate for some, but it
it is less functional and sometimes a bit quirky. Furthermore, because of (current) limitations
of the m2eclipse WTP integration for maven war overlays (which the rave-shindig project uses),
you'll need to use some workarounds to make it workable.
Prerequisite: Install m2eclipse-wtp integration from the m2eclipse-extras [Update Site][10]
-If you already imported the Rave projects in Eclipse, first remove them (but don't need to delete them)
-and then (re)import the Rave project as Maven projects to get the m2eclipse-wtp integration enabled.
+If you already imported the Apache Rave projects in Eclipse, first remove them (but don't need to delete them)
+and then (re)import the Apache Rave project as Maven projects to get the m2eclipse-wtp integration enabled.
Then you need to follow these steps:
@@ -111,7 +111,7 @@ Now we need to add the the two webapps t
## Configuring Intellij
- * Checkout Rave project
+ * Checkout Apache Rave project
* File > New project > Import project from external model and select pom.xml
## Configure remote Tomcat and Intellij
Modified: rave/site/trunk/content/rave/index.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/index.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/index.mdtext (original)
+++ rave/site/trunk/content/rave/index.mdtext Mon Mar 26 18:57:29 2012
@@ -12,14 +12,14 @@ generalization is envisioned to also tra
Wookie.
-## Status of Rave
+## Status of Apache Rave
-Rave brings together and combines several pre-existing projects and teams
+Apache Rave brings together and combines several pre-existing projects and teams
working towards more or less the same or overlapping goals. Each of these projects
is already in production, but Rave is a brand new start. We are bringing together
the best from each of the original projects in a brand new code base.
-The goal for Rave is to become a lightweight and open-standards based extendible
+The goal for Apache Rave is to become a lightweight and open-standards based extendible
platform for using, integrating and hosting OpenSocial and W3C Widget related
features, technologies and services. It will also provide strong context-aware
personalization, collaboration and content integration capabilities and a high
@@ -48,7 +48,7 @@ The intended initial features include:
3. Support for OpenSocial extensions not (yet) defined in the specification
4. Support for other (non-standard, yet) pluggable container services and extensions
-Beyond these initial features the vision and scope for Rave goes much further and
+Beyond these initial features the vision and scope for Apache Rave goes much further and
includes integrating and providing other highly desired/needed features like:
1. native W3C Widgets support through [Apache Wookie][1]
Modified: rave/site/trunk/content/rave/issue-management.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/issue-management.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/issue-management.mdtext (original)
+++ rave/site/trunk/content/rave/issue-management.mdtext Mon Mar 26 18:57:29 2012
@@ -16,12 +16,12 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-All issues are tracked and managed in the Apache JIRA instance ([https://issues.apache.org/jira/browse/rave](https://issues.apache.org/jira/browse/rave)). Please follow the guidelines below when creating issues for Rave in JIRA.
+All issues are tracked and managed in the Apache JIRA instance ([https://issues.apache.org/jira/browse/rave](https://issues.apache.org/jira/browse/rave)). Please follow the guidelines below when creating issues for Apache Rave in JIRA.
####Issue Management Guidelines
* Use the proper issue type
- The Apache JIRA instance defines many types of issues. To keep issue management as simple as possible, the Rave community uses a small subset of the available types. When creating a new issue, please select from the following list the type of issue that best describes the scope and size of the issue:
+ The Apache JIRA instance defines many types of issues. To keep issue management as simple as possible, the Apache Rave community uses a small subset of the available types. When creating a new issue, please select from the following list the type of issue that best describes the scope and size of the issue:
* *Epic*
@@ -51,7 +51,7 @@ All issues are tracked and managed in th
* Assign the correct component
- As Rave becomes more complex, a correctly assigned component will assist the team in identifying and resolving issues.
+ As Apache Rave becomes more complex, a correctly assigned component will assist the team in identifying and resolving issues.
* Assign tasks
Modified: rave/site/trunk/content/rave/mailing-lists.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/mailing-lists.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/mailing-lists.mdtext (original)
+++ rave/site/trunk/content/rave/mailing-lists.mdtext Mon Mar 26 18:57:29 2012
@@ -18,14 +18,14 @@ Notice: Licensed to the Apache Softwa
We welcome you to join our mailing lists and let us know about your thoughts or ideas about Rave.
-### Rave Developer Mailing List
+### Apache Rave Developer Mailing List
This is where the community hangs out. This list is used to coordinate
activities and ensure we are all pulling in the same direction.
- - Subscribe: [rave-dev-subscribe@incubator.apache.org][1]
- - Post (after subscription): [rave-dev@incubator.apache.org][2]
- - Unsubscribe: [rave-dev-unsubscribe@incubator.apache.org][3]
+ - Subscribe: [dev-subscribe@rave.apache.org][1]
+ - Post (after subscription): [dev@rave.apache.org][2]
+ - Unsubscribe: [dev-unsubscribe@rave.apache.org][3]
- Archives
- [Markmail][4]
- [Apache][5]
@@ -35,18 +35,18 @@ activities and ensure we are all pulling
This is where the community receives automated notifications of
any changes to the Rave code and documentation.
- - Subscribe: [rave-commits-subscribe@incubator.apache.org][6]
- - Unsubscribe: [rave-commmits-unsubscribe@incubator.apache.org][7]
+ - Subscribe: [commits-subscribe@rave.apache.org][6]
+ - Unsubscribe: [commmits-unsubscribe@rave.apache.org][7]
- Archives
- [Markmail][8]
- [Apache][9]
- [1]: mailto://rave-dev-subscribe@incubator.apache.org
- [2]: mailto://rave-dev@incubator.apache.org
- [3]: mailto:rave-dev-unsubscribe@incubator.apache.org
+ [1]: mailto:dev-subscribe@rave.apache.org
+ [2]: mailto:dev@rave.apache.org
+ [3]: mailto:dev-unsubscribe@rave.apache.org
[4]: http://markmail.org/search/+list:org.apache.incubator.rave-dev
[5]: http://mail-archives.apache.org/mod_mbox/incubator-rave-dev/
- [6]: mailto:rave-commits-subscribe@incubator.apache.org
- [7]: mailto:rave-commmits-unsubscribe@incubator.apache.org
+ [6]: mailto:commits-subscribe@rave.apache.org
+ [7]: mailto:commmits-unsubscribe@rave.apache.org
[8]: http://markmail.org/search/+list:org.apache.incubator.rave-commits
[9]: http://mail-archives.apache.org/mod_mbox/incubator-rave-commits/
Modified: rave/site/trunk/content/rave/source.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/rave/source.mdtext?rev=1305493&r1=1305492&r2=1305493&view=diff
==============================================================================
--- rave/site/trunk/content/rave/source.mdtext (original)
+++ rave/site/trunk/content/rave/source.mdtext Mon Mar 26 18:57:29 2012
@@ -39,22 +39,22 @@ To build from source code:
* Sources compilation require Java SE 6 or higher.
* The project is built with Apache Maven 3+ (version 3.0.3 or later is *required*) [Download][4] and [install][5]
-### Rave Project
+### Apache Rave Project
-To build the Rave project invoke maven from the project root directory:
+To build the Apache Rave project invoke maven from the project root directory:
- $mvn install
+ mvn install
If you have any problems relating to the rave-master project, see the
-"Rave Master Project" section at the end of this document.
+"Apache Rave Master Project" section at the end of this document.
### Deploying and Running on Tomcat
-To run a local Tomcat instance with rave-shindig and rave-portal deployed:
+To run a local Tomcat instance with rave-shindig and rave-portal and Wookie deployed:
- navigate to the rave-portal subdirectory and invoke:
- `$mvn cargo:start`
+ `mvn cargo:start`
- open url http://localhost:8080/portal in a browser
- press Ctrl-C in the console to stop Tomcat again
@@ -70,14 +70,14 @@ Once the server is running:
* jane.doe
* OpenID: http://rave2011.myopenid.com/ (password rave2011)
-### Rave Master Project
+### Apache Rave Master Project
-The Rave project depends on the separate Rave Master project which defines general and global settings
-for the whole of the Rave project, independent of a specific release. As its rave-master-pom is already published to the
+The Apache Rave project depends on the separate Apache Rave Master project which defines general and global settings
+for the whole of the Apache Rave project, independent of a specific release. As its rave-master-pom is already published to the
Apache Snapshots repository, there is no need to check it out manually and build it locally yourself, unless changes are
needed on general and global level.
-If so needed, the Rave Master project can be checked out from:
+If so needed, the Apache Rave Master project can be checked out from:
http://svn.apache.org/repos/asf/rave/rave-master-pom/trunk rave-master-pom.