aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From z..@apache.org
Subject svn commit: r1040087 [4/5] - in /incubator/aries/branches/site: branches/ images/ resources/ trunk/ trunk/cgi-bin/ trunk/content/ trunk/content/images/ trunk/content/resources/ trunk/lib/ trunk/templates/
Date Mon, 29 Nov 2010 12:32:25 GMT
Added: incubator/aries/branches/site/trunk/content/jndiproject.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/jndiproject.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/jndiproject.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/jndiproject.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,70 @@
+h5. Overview
+
+The Aries JNDI project aims to provide a fully compliant implementation of the OSGi Alliance JNDI Service Specification. This specification details how to advertise InitialContextFactory and ObjectFactories in an OSGi environment. It also defines how to obtain services from the service registry via JNDI.
+
+h5. Service Registry access from JNDI
+
+The OSGi service registry provides a centralised register/query capability for OSGi services. A common pattern outside of OSGi is to make use of the JNDI API to access services from a directory system. The OSGi service registry can be viewed as an example of such a system. The Aries JNDI project provides two URL lookup mechanisms via JNDI that can be used to access the service registry.
+
+h6. osgi:service
+
+The osgi:service lookup scheme is defined by the JNDI Service Specification and follows the scheme:
+
+
+{code}
+osgi:service/<interface>[/<filter>]
+{code}
+The interface part is an interface name, like javax.sql.DataSource, or javax.jms.ConnectionFactory. The filter allows selection based on the properties of the service.
+
+This example:
+
+{code}
+Context ctx = new InitialContext();
+
+Runnable r = (Runnable)ctx.lookup("osgi:service/java.lang.Runnable");
+{code}
+is equivalent to this code written to the OSGi service registry API.
+
+{code}
+BundleContext ctx = getABundleContext();
+ServiceReference ref = ctx.getServiceReference("java.lang.Runnable");
+if (ref != null) {
+  Runnable r = ctx.getService(ref);
+}
+{code}
+
+Lets say you wanted to filter for a Runnable with a property called _fred_ which was mapped to _wilma_. You could write
+
+{code}
+Context ctx = new InitialContext();
+
+Runnable r = (Runnable)ctx.lookup("osgi:service/java.lang.Runnable/(fred=wilma)");
+{code}
+
+which is equivalent to:
+
+{code}
+BundleContext ctx = getABundleContext();
+ServiceReference[] refs = ctx.getServiceReference("java.lang.Runnable", "(fred=wilma)");
+if (refs != null) {
+  Runnable r = ctx.getService(refs[refs.length - 1]);
+}
+{code}
+
+The osgi:service namepsace returns proxies, so if the Runnable was unregistered the proxy would switch to an equivalent alternative. If no such alternative exists then an org.osgi.framework.ServiceException with a type of ServiceException.UNREGISTERED.
+
+h6. osgi:servicelist
+
+It is possible that there are multiple services in the registry that match. In this case the osgi:servicelist lookup scheme can be used. It has the same format as osgi:service, but it is designed to return multiple.
+
+h6. aries:services
+
+The aries:services scheme works in the same way as the osgi:service scheme, but does not perform proxying. You get the actual object back. Care must be taken with this approach as the service could be unregistered, but the client cannot tell to stop using it. As a result it should only be used if the service is to be used for a short period of time. In addition their is no way to indicate that the client is no longer using the service, so clean up cannot occur.
+
+
+
+h5. More Information
+
+
+
+For more information, check out section "126 JNDI Services Specification Version 1.0" in the "OSGi Service Platform Enterprise Specification, Release 4, Version 4.2" available for public download from the [OSGi Alliance|http://www.osgi.org/Download/Release4V42].
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/jndiproject.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/jndiproject.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/jndiproject.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/jndiproject.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,107 @@
+Title: JNDIProject
+<a name="JNDIProject-Overview"></a>
+##### Overview
+
+The Aries JNDI project aims to provide a fully compliant implementation of
+the OSGi Alliance JNDI Service Specification. This specification details
+how to advertise InitialContextFactory and ObjectFactories in an OSGi
+environment. It also defines how to obtain services from the service
+registry via JNDI.
+
+<a name="JNDIProject-ServiceRegistryaccessfromJNDI"></a>
+##### Service Registry access from JNDI
+
+The OSGi service registry provides a centralised register/query capability
+for OSGi services. A common pattern outside of OSGi is to make use of the
+JNDI API to access services from a directory system. The OSGi service
+registry can be viewed as an example of such a system. The Aries JNDI
+project provides two URL lookup mechanisms via JNDI that can be used to
+access the service registry.
+
+<a name="JNDIProject-osgi:service"></a>
+###### osgi:service
+
+The osgi:service lookup scheme is defined by the JNDI Service Specification
+and follows the scheme:
+
+
+{code}
+osgi:service/<interface>[/<filter>](/<filter>.html)
+{code}
+The interface part is an interface name, like javax.sql.DataSource, or
+javax.jms.ConnectionFactory. The filter allows selection based on the
+properties of the service.
+
+This example:
+
+{code}
+Context ctx = new InitialContext();
+
+Runnable r = (Runnable)ctx.lookup("osgi:service/java.lang.Runnable");
+{code}
+is equivalent to this code written to the OSGi service registry API.
+
+{code}
+BundleContext ctx = getABundleContext();
+ServiceReference ref = ctx.getServiceReference("java.lang.Runnable");
+if (ref != null) {
+  Runnable r = ctx.getService(ref);
+}
+{code}
+
+Lets say you wanted to filter for a Runnable with a property called _fred_
+which was mapped to _wilma_. You could write
+
+{code}
+Context ctx = new InitialContext();
+
+Runnable r =
+(Runnable)ctx.lookup("osgi:service/java.lang.Runnable/(fred=wilma)");
+{code}
+
+which is equivalent to:
+
+{code}
+BundleContext ctx = getABundleContext();
+ServiceReference[](.html)
+ refs = ctx.getServiceReference("java.lang.Runnable", "(fred=wilma)");
+if (refs != null) {
+  Runnable r = ctx.getService(refs[refs.length - 1](refs.length---1.html)
+);
+}
+{code}
+
+The osgi:service namepsace returns proxies, so if the Runnable was
+unregistered the proxy would switch to an equivalent alternative. If no
+such alternative exists then an org.osgi.framework.ServiceException with a
+type of ServiceException.UNREGISTERED.
+
+<a name="JNDIProject-osgi:servicelist"></a>
+###### osgi:servicelist
+
+It is possible that there are multiple services in the registry that match.
+In this case the osgi:servicelist lookup scheme can be used. It has the
+same format as osgi:service, but it is designed to return multiple.
+
+<a name="JNDIProject-aries:services"></a>
+###### aries:services
+
+The aries:services scheme works in the same way as the osgi:service scheme,
+but does not perform proxying. You get the actual object back. Care must be
+taken with this approach as the service could be unregistered, but the
+client cannot tell to stop using it. As a result it should only be used if
+the service is to be used for a short period of time. In addition their is
+no way to indicate that the client is no longer using the service, so clean
+up cannot occur.
+
+
+
+<a name="JNDIProject-MoreInformation"></a>
+##### More Information
+
+
+
+For more information, check out section "126 JNDI Services Specification
+Version 1.0" in the "OSGi Service Platform Enterprise Specification,
+Release 4, Version 4.2" available for public download from the [OSGi Alliance](http://www.osgi.org/Download/Release4V42)
+.

Added: incubator/aries/branches/site/trunk/content/jpaproject.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/jpaproject.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/jpaproject.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/jpaproject.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,4 @@
+The Aries JPA project will make it easy for JPA persistence providers such as [Apache OpenJPA|http://openjpa.apache.org/] to be used in an OSGi environment and will provide container managed persistence for the Blueprint container.
+
+For more information, check out section "127 JPA Service Specification Version 1.0" in the "OSGi Service Platform Enterprise Specification, Release 4, Version 4.2" available for public download from the [OSGi Alliance|http://www.osgi.org/Download/Release4V42].
+

Added: incubator/aries/branches/site/trunk/content/jpaproject.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/jpaproject.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/jpaproject.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/jpaproject.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,11 @@
+Title: JPAProject
+The Aries JPA project will make it easy for JPA persistence providers such
+as [Apache OpenJPA](http://openjpa.apache.org/)
+ to be used in an OSGi environment and will provide container managed
+persistence for the Blueprint container.
+
+For more information, check out section "127 JPA Service Specification
+Version 1.0" in the "OSGi Service Platform Enterprise Specification,
+Release 4, Version 4.2" available for public download from the [OSGi Alliance](http://www.osgi.org/Download/Release4V42)
+.
+

Added: incubator/aries/branches/site/trunk/content/june-2010.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/june-2010.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/june-2010.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/june-2010.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,25 @@
+Aries will deliver a set of pluggable Java components enabling an enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009.
+
+There are currently no issues requiring IPMC or Board attention.
+
+The following sub-components are actively being developed:
+
+* Application
+* Subsystems
+* Blueprint
+* JMX
+* JPA
+
+Several new sample applications have been developed to demonstrate the Aries functionality.
+
+There continues to be a vibrant community as shown by the activity on the mailing list this year.
+
+On May 26th we released Apache Aries 0.1-incubating, our first release.
+
+Top 2 or 3 things to resolve before graduation:
+
+* Build community  [done]
+* Create a release [done]
+* Address project scope concerns raised during acceptance vote
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/june-2010.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/june-2010.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/june-2010.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/june-2010.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,29 @@
+Title: June 2010
+Aries will deliver a set of pluggable Java components enabling an
+enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009.
+
+There are currently no issues requiring IPMC or Board attention.
+
+The following sub-components are actively being developed:
+
+* Application
+* Subsystems
+* Blueprint
+* JMX
+* JPA
+
+Several new sample applications have been developed to demonstrate the
+Aries functionality.
+
+There continues to be a vibrant community as shown by the activity on the
+mailing list this year.
+
+On May 26th we released Apache Aries 0.1-incubating, our first release.
+
+Top 2 or 3 things to resolve before graduation:
+
+* Build community  [done](done.html)
+* Create a release [done](done.html)
+* Address project scope concerns raised during acceptance vote

Added: incubator/aries/branches/site/trunk/content/mailinglists.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/mailinglists.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/mailinglists.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/mailinglists.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,20 @@
+The Aries User list is for general discussion or questions on using any of the Aries sub-projects. Aries developers monitor this list and provide assistance when needed.
+
+ * [Subscribe|mailto:aries-user-subscribe@incubator.apache.org] to the Aries User list
+ * [Unsubscribe|mailto:aries-user-unsubscribe@incubator.apache.org] from the Aries User list
+ * [Post|mailto:aries-user@incubator.apache.org] to the Aries User list
+ * [View|http://mail-archives.apache.org/mod_mbox/incubator-aries-user/] to the Aries User list archive
+
+The Aries Developer list is for developers to discuss ongoing work, make decisions and vote on technical issues. There is one list for all Aries sub-projects.
+
+ * [Subscribe|mailto:aries-dev-subscribe@incubator.apache.org] to the Aries Developer list
+ * [Unsubscribe|mailto:aries-dev-unsubscribe@incubator.apache.org] from the Aries Developer list
+ * [Post|mailto:aries-dev@incubator.apache.org] to the Aries Developer list
+ * [View|http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/] to the Aries Developer list archive
+
+The Aries Commits list receives notifications when changes are committed to the Aries source tree.
+
+ * [Subscribe|mailto:aries-commits-subscribe@incubator.apache.org] to the Aries Commits list
+ * [Unsubscribe|mailto:aries-commits-unsubscribe@incubator.apache.org] from the Aries Commits list
+ * [Post|mailto:aries-commits@incubator.apache.org] to the Aries Commits list
+ * [View|http://mail-archives.apache.org/mod_mbox/incubator-aries-commits/] to the Aries Commits list archive
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/mailinglists.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/mailinglists.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/mailinglists.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/mailinglists.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,38 @@
+Title: MailingLists
+The Aries User list is for general discussion or questions on using any of
+the Aries sub-projects. Aries developers monitor this list and provide
+assistance when needed.
+
+ * [Subscribe](mailto:aries-user-subscribe@incubator.apache.org.html)
+ to the Aries User list
+ * [Unsubscribe](mailto:aries-user-unsubscribe@incubator.apache.org.html)
+ from the Aries User list
+ * [Post](mailto:aries-user@incubator.apache.org.html)
+ to the Aries User list
+ * [View](http://mail-archives.apache.org/mod_mbox/incubator-aries-user/)
+ to the Aries User list archive
+
+The Aries Developer list is for developers to discuss ongoing work, make
+decisions and vote on technical issues. There is one list for all Aries
+sub-projects.
+
+ * [Subscribe](mailto:aries-dev-subscribe@incubator.apache.org.html)
+ to the Aries Developer list
+ * [Unsubscribe](mailto:aries-dev-unsubscribe@incubator.apache.org.html)
+ from the Aries Developer list
+ * [Post](mailto:aries-dev@incubator.apache.org.html)
+ to the Aries Developer list
+ * [View](http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/)
+ to the Aries Developer list archive
+
+The Aries Commits list receives notifications when changes are committed to
+the Aries source tree.
+
+ * [Subscribe](mailto:aries-commits-subscribe@incubator.apache.org.html)
+ to the Aries Commits list
+ * [Unsubscribe](mailto:aries-commits-unsubscribe@incubator.apache.org.html)
+ from the Aries Commits list
+ * [Post](mailto:aries-commits@incubator.apache.org.html)
+ to the Aries Commits list
+ * [View](http://mail-archives.apache.org/mod_mbox/incubator-aries-commits/)
+ to the Aries Commits list archive

Added: incubator/aries/branches/site/trunk/content/maintainingthewebpages.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/maintainingthewebpages.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/maintainingthewebpages.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/maintainingthewebpages.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,45 @@
+h1. How the Aries web site works
+
+The Aries web site is built from a Confluence wiki. A Confluence plug-in, the auto-export plug-in, exports the wiki pages to html. The exported html is rsync'd once an hour with the web site directory on Minotaur, this in turn is rsync'd once an hour with the public facing web servers eos and aurora. The style sheet is extracted from SVN and is also applied to the web site once an hour. This means that when changes are made to the wiki will they may take up to two hours to propagate to the web site.
+
+This page gives a more detailed description of how the process works and what you can expect to see. 
+
+h3. The details
+
+h5. The wiki pages
+Any Aries committer can update the web site, in addition to their Apache UID they also need a Confluence user ID and password. Somewhere on the web site you will find an 'edit' button, if a committer selects the button it will take them to the wiki edit pages, or, if they don't have a Confluence ID it will take them to a page where they can request an ID. If you are making changes please:
+* Add new pages in a logical place in the site. For example, 'People' is a child page of 'Community'
+* Avoid spaces in page names
+* Confluence has a single name space per site - so choose page names which stand a good chance of being unique. 
+
+h5. Saving changes
+When you have finished editing the wiki, save the changes and the auto-export plugin will take care of exporting the html. If you want to see where it is exported to:
+{code}
+ssh people.apache.org
+ls -latr /www/confluence-exports/ARIES
+{code}
+
+h5. Why does the web site look like a wiki still?
+Magic. The auto-export plugin needs a template, but only someone with Confluence Admin rights can apply it. The templates look like Velocity templates - but of course you can't see them unless you have Confluence Admin rights :-). However to preserve history and just in case there is an issue in Confluence we keep a copy of the auto-export template in svn at  https://svn.apache.org/repos/asf/incubator/aries/site/template/ARIES_autoexport_template.xml
+
+These templates are fairly common and projects often copy them when they find one they like.  For Aries, we used the template from ServiceMix, but we could have used the one from Tuscany or any of the projects that run their sites this way. 
+
+Here is a [list|http://cwiki.apache.org/confluence/administrators.action] of people with Confluence Admin rights if you need to update or modify the template.  Please be sure to save any future changes in the auto-export template at the svn location mentioned.
+
+h5. How do the HTML pages get to their final location - and where is that exactly?
+Simple. You or someone on the project, needs to set up a cron job which rsyncs the directory that the wiki exports to with the real web site directory. For example, on people.apache.org:
+{code}
+'0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/ARIES/ /www/incubator.apache.org/aries/)
+{code}
+
+Another cron job will rsync the web site directory om minotaur with the public facing Apache web servers (eos and aurora). If this step seems to be failing you will need to mail the infra@ list.
+
+h5. What about style sheets?
+The style sheet (site.css) is applied to the final minotaur destination, /www/incubator.apache.org/aries/ by extracting it from [SVN|https://svn.apache.org/repos/asf/incubator/aries/site/]. The style sheet, not the template, provides most of the look and feel of the site.
+
+h5. What do I do when it goes wrong?
+Check the content of the wiki export and the web site directories. Make sure that your changes were saved and check that the cron job has run. If it looks like a Confluence issue or an issue with synching to the public facing web servers mail the [infra|mailto:infrastructure@apache.org] list and ask for help.
+
+
+
+

Added: incubator/aries/branches/site/trunk/content/maintainingthewebpages.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/maintainingthewebpages.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/maintainingthewebpages.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/maintainingthewebpages.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,93 @@
+Title: MaintainingTheWebPages
+<a name="MaintainingTheWebPages-HowtheArieswebsiteworks"></a>
+# How the Aries web site works
+
+The Aries web site is built from a Confluence wiki. A Confluence plug-in,
+the auto-export plug-in, exports the wiki pages to html. The exported html
+is rsync'd once an hour with the web site directory on Minotaur, this in
+turn is rsync'd once an hour with the public facing web servers eos and
+aurora. The style sheet is extracted from SVN and is also applied to the
+web site once an hour. This means that when changes are made to the wiki
+will they may take up to two hours to propagate to the web site.
+
+This page gives a more detailed description of how the process works and
+what you can expect to see. 
+
+<a name="MaintainingTheWebPages-Thedetails"></a>
+### The details
+
+<a name="MaintainingTheWebPages-Thewikipages"></a>
+##### The wiki pages
+Any Aries committer can update the web site, in addition to their Apache
+UID they also need a Confluence user ID and password. Somewhere on the web
+site you will find an 'edit' button, if a committer selects the button it
+will take them to the wiki edit pages, or, if they don't have a Confluence
+ID it will take them to a page where they can request an ID. If you are
+making changes please:
+* Add new pages in a logical place in the site. For example, 'People' is a
+child page of 'Community'
+* Avoid spaces in page names
+* Confluence has a single name space per site - so choose page names which
+stand a good chance of being unique. 
+
+<a name="MaintainingTheWebPages-Savingchanges"></a>
+##### Saving changes
+When you have finished editing the wiki, save the changes and the
+auto-export plugin will take care of exporting the html. If you want to see
+where it is exported to:
+{code}
+ssh people.apache.org
+ls -latr /www/confluence-exports/ARIES
+{code}
+
+<a name="MaintainingTheWebPages-Whydoesthewebsitelooklikeawikistill?"></a>
+##### Why does the web site look like a wiki still?
+Magic. The auto-export plugin needs a template, but only someone with
+Confluence Admin rights can apply it. The templates look like Velocity
+templates - but of course you can't see them unless you have Confluence
+Admin rights :-). However to preserve history and just in case there is an
+issue in Confluence we keep a copy of the auto-export template in svn at 
+https://svn.apache.org/repos/asf/incubator/aries/site/template/ARIES_autoexport_template.xml
+
+These templates are fairly common and projects often copy them when they
+find one they like.  For Aries, we used the template from ServiceMix, but
+we could have used the one from Tuscany or any of the projects that run
+their sites this way. 
+
+Here is a [list](http://cwiki.apache.org/confluence/administrators.action)
+ of people with Confluence Admin rights if you need to update or modify the
+template.  Please be sure to save any future changes in the auto-export
+template at the svn location mentioned.
+
+h5. How do the HTML pages get to their final location - and where is that
+exactly?
+Simple. You or someone on the project, needs to set up a cron job which
+rsyncs the directory that the wiki exports to with the real web site
+directory. For example, on people.apache.org:
+{code}
+'0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/ARIES/
+/www/incubator.apache.org/aries/)
+{code}
+
+Another cron job will rsync the web site directory om minotaur with the
+public facing Apache web servers (eos and aurora). If this step seems to be
+failing you will need to mail the infra@ list.
+
+<a name="MaintainingTheWebPages-Whataboutstylesheets?"></a>
+##### What about style sheets?
+The style sheet (site.css) is applied to the final minotaur destination,
+/www/incubator.apache.org/aries/ by extracting it from [SVN](https://svn.apache.org/repos/asf/incubator/aries/site/)
+. The style sheet, not the template, provides most of the look and feel of
+the site.
+
+<a name="MaintainingTheWebPages-WhatdoIdowhenitgoeswrong?"></a>
+##### What do I do when it goes wrong?
+Check the content of the wiki export and the web site directories. Make
+sure that your changes were saved and check that the cron job has run. If
+it looks like a Confluence issue or an issue with synching to the public
+facing web servers mail the [infra](mailto:infrastructure@apache.org.html)
+ list and ask for help.
+
+
+
+

Added: incubator/aries/branches/site/trunk/content/march-2010.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/march-2010.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/march-2010.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/march-2010.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,28 @@
+Aries will deliver a set of pluggable Java components enabling an enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009.
+
+There are currently no issues requiring IPMC or Board attention .
+
+The following sub-components are actively being developed:
+
+* Application
+* Blueprint
+* JMX
+* JPA
+
+Several new sample applications have been developed to demonstrate the Aries functionality.
+
+A new component has been created to feed experience into the OSGi standards process.
+
+There has been a lot of activity on the mailing list this year indicating a vibrant community is being built.
+
+One new committer, Rex Wang, has been added. Redhat have started to participate in the project.
+
+We have begun the process of doing a 0.1.0 release and aim to release shortly.
+
+Top 2 or 3 things to resolve before graduation:
+
+* Build community
+* Create a release
+* Address project scope concerns raised during acceptance vote
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/march-2010.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/march-2010.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/march-2010.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/march-2010.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,35 @@
+Title: March 2010
+Aries will deliver a set of pluggable Java components enabling an
+enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009.
+
+There are currently no issues requiring IPMC or Board attention .
+
+The following sub-components are actively being developed:
+
+* Application
+* Blueprint
+* JMX
+* JPA
+
+Several new sample applications have been developed to demonstrate the
+Aries functionality.
+
+A new component has been created to feed experience into the OSGi standards
+process.
+
+There has been a lot of activity on the mailing list this year indicating a
+vibrant community is being built.
+
+One new committer, Rex Wang, has been added. Redhat have started to
+participate in the project.
+
+We have begun the process of doing a 0.1.0 release and aim to release
+shortly.
+
+Top 2 or 3 things to resolve before graduation:
+
+* Build community
+* Create a release
+* Address project scope concerns raised during acceptance vote

Added: incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,27 @@
+
+h1. Assembled best practice notes
+
+h3. Overall structure
+
+The Aries project is a collection of loosely couple sub-projects, therefore it must be possible to build each project on it's own. This implies:
+
+# A parent pom that isn't at the root of the SVN trunk
+# Each sub-project has enough pom info so that it can be released independently
+# default-parent has dependency management for basic osgi-dependencies that all projects are almost certain to use (this includes PAX dependencies for testing)
+# Each sub-project has legal files in its checkout root
+# Each sub-project has an SCM element in its pom, but no others do.
+# Each subproject has dependency management for everything included in it.  In addition, it has its subprojects listed in dependency management.  This means that
+## modules in a subproject don't need to include versions for use of other modules
+## you can get dependency management for all the modules in a subproject by depending on the subproject pom with scope import  (see the samples pom for an example).
+# As a result of the above, modules don't have any versions in any dependency elements
+
+h3. Good practice in the pom
+
+# Alphabetic ordering in dependency management
+# Include a brief description of the project
+# Commenting in platform dependencies, see samples assembly projects.
+
+h3. Group and Artifact names 
+# The Bundle Symbolic Name is explicitly set to the Maven artifactId. For projects which deliver bundles, the artifactID will therefore completely describe the jar and must begin org.apache.aries.\{subproject\}. For projects which do not deliver bundles (for example agregator projects) it is acceptable to use a short descriptive artifactID.
+# The group ID will overlap with the artifactId and will normally be of the form org.apache.aries.\{subproject\}
+

Added: incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,47 @@
+Title: Maven best practice in Aries
+
+<a name="MavenbestpracticeinAries-Assembledbestpracticenotes"></a>
+# Assembled best practice notes
+
+<a name="MavenbestpracticeinAries-Overallstructure"></a>
+### Overall structure
+
+The Aries project is a collection of loosely couple sub-projects, therefore
+it must be possible to build each project on it's own. This implies:
+
+1. A parent pom that isn't at the root of the SVN trunk
+1. Each sub-project has enough pom info so that it can be released
+independently
+1. default-parent has dependency management for basic osgi-dependencies that
+all projects are almost certain to use (this includes PAX dependencies for
+testing)
+1. Each sub-project has legal files in its checkout root
+1. Each sub-project has an SCM element in its pom, but no others do.
+1. Each subproject has dependency management for everything included in it. 
+In addition, it has its subprojects listed in dependency management.  This
+means that
+1. # modules in a subproject don't need to include versions for use of other
+modules
+1. # you can get dependency management for all the modules in a subproject by
+depending on the subproject pom with scope import  (see the samples pom for
+an example).
+1. As a result of the above, modules don't have any versions in any
+dependency elements
+
+<a name="MavenbestpracticeinAries-Goodpracticeinthepom"></a>
+### Good practice in the pom
+
+1. Alphabetic ordering in dependency management
+1. Include a brief description of the project
+1. Commenting in platform dependencies, see samples assembly projects.
+
+<a name="MavenbestpracticeinAries-GroupandArtifactnames"></a>
+### Group and Artifact names 
+1. The Bundle Symbolic Name is explicitly set to the Maven artifactId. For
+projects which deliver bundles, the artifactID will therefore completely
+describe the jar and must begin org.apache.aries.\{subproject\}. For
+projects which do not deliver bundles (for example agregator projects) it
+is acceptable to use a short descriptive artifactID.
+1. The group ID will overlap with the artifactId and will normally be of the
+form org.apache.aries.\{subproject\}
+

Added: incubator/aries/branches/site/trunk/content/moduledependencies.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/moduledependencies.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/moduledependencies.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/moduledependencies.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,5 @@
+h1. Module build time dependencies
+
+There are build time dependencies between Aries modules. This diagram shows the dependencies. For example, if you need to build 0.2-incubating JPA module you will find that you need to have built (or have available) parent, testsupport, util, blueprint, quiesce and transaction at the level specified in the pom.xml for the JPA module.
+
+!AriseBuildDeps.png!
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/moduledependencies.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/moduledependencies.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/moduledependencies.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/moduledependencies.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,11 @@
+Title: ModuleDependencies
+<a name="ModuleDependencies-Modulebuildtimedependencies"></a>
+# Module build time dependencies
+
+There are build time dependencies between Aries modules. This diagram shows
+the dependencies. For example, if you need to build 0.2-incubating JPA
+module you will find that you need to have built (or have available)
+parent, testsupport, util, blueprint, quiesce and transaction at the level
+specified in the pom.xml for the JPA module.
+
+!AriseBuildDeps.png!

Added: incubator/aries/branches/site/trunk/content/modules.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/modules.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/modules.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/modules.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,11 @@
+h1. Modules
+
+ - [Samples]
+ - [Blueprint|Blueprint]
+ ** [Blueprint annotations|BlueprintAnnotation]
+ - [JNDI|JNDIProject]
+ - [JPA|JPAProject]
+ - [Transactions|TransactionsProject]
+ - [Applications|Applications]
+ - [EBA Maven Plugin|EBAMavenPluginProject]
+ - [SPI Fly]
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/modules.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/modules.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/modules.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/modules.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,13 @@
+Title: Modules
+<a name="Modules-Modules"></a>
+# Modules
+
+ - [Samples](samples.html)
+ - [Blueprint](blueprint.html)
+ ** [Blueprint annotations](blueprintannotation.html)
+ - [JNDI](jndiproject.html)
+ - [JPA](jpaproject.html)
+ - [Transactions](transactionsproject.html)
+ - [Applications](applications.html)
+ - [EBA Maven Plugin](ebamavenpluginproject.html)
+ - [SPI Fly](spi-fly.html)

Added: incubator/aries/branches/site/trunk/content/navigation.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/navigation.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/navigation.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/navigation.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,42 @@
+* h3. [Overview|Overview]
+** h4. [Board Reports|BoardReports]
+** h4. [Site Map|SiteMap]
+
+* h3. [Documentation]
+ ** h4. [Programming Model|AriesProgrammingModel]
+ ** h4. [Pointers to OSGi specs|PointersToOSGiSpecifications]
+ ** h4. [Integrators Guide|Integrators Guide]
+ ** h4. [Articles]
+ ** h4. [Slides|https://svn.apache.org/repos/asf/incubator/aries/slides/]
+ ** h4. [Tutorials]
+
+* h3. [Downloads]
+
+* h3. [Community]
+ ** h4. [Getting Involved|GettingInvolved]
+ ** h4. [Who we are|People]
+ ** h4. [Mailing lists|MailingLists]
+ ** h4. [Aries Group Blog|http://blogs.apache.org/aries/]
+
+
+* h3. [Development] 
+** h4. [Source Control | https://svn.apache.org/repos/asf/incubator/aries/]
+** h4. [Bug Tracking| https://issues.apache.org/jira/browse/ARIES]
+** h4. [Building Aries | BuildingAries]
+** h4. [Releasing Aries | ReleasingAries]
+** h4. [OSGi Compliance Tests | ComplianceTesting]
+** h4. [Build System| http://hudson.zones.apache.org/hudson/]
+** h4. [Web Site Maintenance | MaintainingTheWebPages]
+
+* h3. [Modules]
+** h4. [Samples]
+** h4. [Blueprint|Blueprint]
+** h4. [JNDI|JNDIproject]
+** h4. [JPA|JPAproject]
+** h4. [Applications|Applications]
+** h4. [Transactions|TransactionsProject]
+** h4. [EBA Maven Plugin | EBAMavenPluginProject]
+** h4. [SPI Fly]
+
+* h3. [Sponsorship]
+

Added: incubator/aries/branches/site/trunk/content/navigation.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/navigation.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/navigation.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/navigation.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,43 @@
+Title: Navigation
+* h3. [Overview](overview.html)
+** h4. [Board Reports](boardreports.html)
+** h4. [Site Map](sitemap.html)
+
+* h3. [Documentation](documentation.html)
+ ** h4. [Programming Model](ariesprogrammingmodel.html)
+ ** h4. [Pointers to OSGi specs](pointerstoosgispecifications.html)
+ ** h4. [Integrators Guide](integrators-guide.html)
+ ** h4. [Articles](articles.html)
+ ** h4. [Slides](https://svn.apache.org/repos/asf/incubator/aries/slides/)
+ ** h4. [Tutorials](tutorials.html)
+
+* h3. [Downloads](downloads.html)
+
+* h3. [Community](community.html)
+ ** h4. [Getting Involved](gettinginvolved.html)
+ ** h4. [Who we are](people.html)
+ ** h4. [Mailing lists](mailinglists.html)
+ ** h4. [Aries Group Blog](http://blogs.apache.org/aries/)
+
+
+* h3. [Development](development.html)
+** h4. [Source Control ](-https://svn.apache.org/repos/asf/incubator/aries/.html)
+** h4. [Bug Tracking](-https://issues.apache.org/jira/browse/aries.html)
+** h4. [Building Aries ](-buildingaries.html)
+** h4. [Releasing Aries ](-releasingaries.html)
+** h4. [OSGi Compliance Tests ](-compliancetesting.html)
+** h4. [Build System](-http://hudson.zones.apache.org/hudson/.html)
+** h4. [Web Site Maintenance ](-maintainingthewebpages.html)
+
+* h3. [Modules](modules.html)
+** h4. [Samples](samples.html)
+** h4. [Blueprint](blueprint.html)
+** h4. [JNDI](jndiproject.html)
+** h4. [JPA](jpaproject.html)
+** h4. [Applications](applications.html)
+** h4. [Transactions](transactionsproject.html)
+** h4. [EBA Maven Plugin ](-ebamavenpluginproject.html)
+** h4. [SPI Fly](spi-fly.html)
+
+* h3. [Sponsorship](sponsorship.html)
+

Added: incubator/aries/branches/site/trunk/content/november-2009.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/november-2009.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/november-2009.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/november-2009.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,17 @@
+Aries will deliver a set of pluggable Java components enabling an enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009. This is our second board report.
+
+There are currently no issues requiring IPMC or Board attention .
+
+The svn area has been organized with a single trunk for now, though we still need to settle the discussion about components lifecycle and the svn layout.
+
+The application manifest component of the IBM contribution has been moved out into the trunk. The blueprint component has undergone some further enhancement and work is starting on an implementation of the OSGi JMX specification.
+
+The mailing lists was quieter this month, probably due to the apache conference.
+
+Top 2 or 3 things to resolve before graduation:
+
+Build community
+Create a release
+Address project scope concerns raised during acceptance vote
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/november-2009.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/november-2009.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/november-2009.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/november-2009.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,26 @@
+Title: November 2009
+Aries will deliver a set of pluggable Java components enabling an
+enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009. This is our second board
+report.
+
+There are currently no issues requiring IPMC or Board attention .
+
+The svn area has been organized with a single trunk for now, though we
+still need to settle the discussion about components lifecycle and the svn
+layout.
+
+The application manifest component of the IBM contribution has been moved
+out into the trunk. The blueprint component has undergone some further
+enhancement and work is starting on an implementation of the OSGi JMX
+specification.
+
+The mailing lists was quieter this month, probably due to the apache
+conference.
+
+Top 2 or 3 things to resolve before graduation:
+
+Build community
+Create a release
+Address project scope concerns raised during acceptance vote

Added: incubator/aries/branches/site/trunk/content/october-2009.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/october-2009.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/october-2009.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/october-2009.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,18 @@
+Aries will deliver a set of pluggable Java components enabling an enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009. This is our first board report.
+
+There are currently no issues requiring IPMC or Board attention .
+
+All infra resources have been set up (svn / site / mailing lists) very quickly.
+The svn area has been organized with a single trunk for now, though we still need to settle the discussion about components lifecycle and the svn layout.
+IBM has contributed some code that has been imported into svn and the JNDI modules have already been imported into trunk.  Both Geronimo contribution (OSGi Blueprint Services) and ServiceMix contribution (OSGi Transaction Manager) have been imported into trunk.
+
+On the community side, we've already voted 3 additional committers (Adam Wojtuniak, Alan Keane and Niclas Hedhman) who had expressed their interest in joining the project just after the acceptance vote on the proposal was launched.
+
+There is a lot of discussions and activity on the mailing lists.
+
+Top 2 or 3 things to resolve before graduation:
+* Build community
+* Create a release 
+* Address project scope concerns raised during acceptance vote
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/october-2009.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/october-2009.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/october-2009.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/october-2009.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,30 @@
+Title: October 2009
+Aries will deliver a set of pluggable Java components enabling an
+enterprise OSGi application programming model.
+
+Aries entered incubation on September 22, 2009. This is our first board
+report.
+
+There are currently no issues requiring IPMC or Board attention .
+
+All infra resources have been set up (svn / site / mailing lists) very
+quickly.
+The svn area has been organized with a single trunk for now, though we
+still need to settle the discussion about components lifecycle and the svn
+layout.
+IBM has contributed some code that has been imported into svn and the JNDI
+modules have already been imported into trunk.	Both Geronimo contribution
+(OSGi Blueprint Services) and ServiceMix contribution (OSGi Transaction
+Manager) have been imported into trunk.
+
+On the community side, we've already voted 3 additional committers (Adam
+Wojtuniak, Alan Keane and Niclas Hedhman) who had expressed their interest
+in joining the project just after the acceptance vote on the proposal was
+launched.
+
+There is a lot of discussions and activity on the mailing lists.
+
+Top 2 or 3 things to resolve before graduation:
+* Build community
+* Create a release 
+* Address project scope concerns raised during acceptance vote

Added: incubator/aries/branches/site/trunk/content/overview.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/overview.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/overview.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/overview.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,5 @@
+h1. Overview
+
+- [Board Reports|BoardReports]
+- [License|http://www.apache.org/licenses/LICENSE-2.0.html]
+- [Site Map|SiteMap]

Added: incubator/aries/branches/site/trunk/content/overview.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/overview.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/overview.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/overview.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,7 @@
+Title: Overview
+<a name="Overview-Overview"></a>
+# Overview
+
+- [Board Reports](boardreports.html)
+- [License](http://www.apache.org/licenses/LICENSE-2.0.html)
+- [Site Map](sitemap.html)

Added: incubator/aries/branches/site/trunk/content/people.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/people.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/people.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/people.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,51 @@
+This is a list of the people involved in the Apache Aries Incubator and their roles.
+
+||Name||Organization||PPMC Member||Mentor||Champion||IPMC
+|Adam Wojtuniak |Ericsson | | | | |
+|Alan Cabrera|LinkedIn| (/)| | | (/) |
+|Alan Keane|Ericsson | | | | |
+|Alasdair Nottingham|IBM| (/)| | | |
+|Andrew Osborne|IBM| (/)| | | |
+|Bartosz Kowalewski| | | | | |
+|Bernd Kolb|SAP| (/)| | | |
+|Bertrand Delacretaz| | (/)|(/) emeritus| | (/) |
+|Carsten Ziegeler| | (/)| | | |
+|Chris Wilkinson|IBM| | | | |
+|Dan Kulp|Progress| (/)| | | (/) |
+|David Bosschaert|Red Hat| (/)| | |	 |
+|David Jencks|IBM| (/)	| | | |
+|Davanum Srinivas (Dims)|IBM|(/)|(/)| | (/) |
+|Dimo Stoilov|SAP| (/)	| | | |
+|Emily Jiang|IBM| | | | |
+|Eoghan Glynn|Progress| (/)|	| | |
+|Graham Charters|IBM| (/)|	| | |
+|Guillaume Nodet|Progress| (/)|(/)|(/)|(/)|
+|Hiram Chirino|Progress| (/)	| | | |
+|Holly Cummins|IBM| | | | |
+|Ian Robinson|IBM| (/)	| | | |
+|James Strachan|Progress| (/)|	| | (/) |
+|Jarek Gawor|IBM| (/)	| | | (/) |
+|Jean-Sebastien Delfino|IBM| (/)	| | | |
+|Jeremy Hughes|IBM| (/)	| | | |
+|Joe Bohn|IBM| (/)	| | | |
+|Kevan Miller|IBM|(/)|(/)|(/)|(/)|
+|Lei "Rex" Wang|IBM| | | | |
+|Lin Sun|IBM| (/)	| | | |
+|Kiril Mitov|SAP| (/)	| | | |
+|Mark Nuttall|IBM| (/)	| | | |
+|Niclas Hedhman| | 	| | |(/)|
+|Niklas Gustavsson| | (/)| | |	 |
+|Nikolai Tankov|SAP| (/)| | |	 |
+|Oisin Hurley|Progress| (/)| | | |	
+|Peter Peshev|SAP| (/)	| | | |
+|Raymond Feng|IBM| (/)	| | | |
+|Rick McGuire|IBM| (/)	| | | |
+|Roman Roelofsen|ProSyst| (/)| | | |	
+|Sabine Heider|SAP| (/)	| | | |
+|Sergey Beryozkin|Progress| (/)| | | |	
+|Stuart McCulloch| | (/)	| | | |
+|Timothy Ward|IBM| (/)	| | | |
+|Todor Boev|ProSyst| (/)| | |	 |
+|Valentin Mahrwald|IBM| (/)| | | |	
+|Violeta Georgieva|SAP| (/)| | | |	
+|Zoe Slattery|IBM| (/)	| | | |
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/people.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/people.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/people.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/people.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,55 @@
+Title: People
+This is a list of the people involved in the Apache Aries Incubator and
+their roles.
+
+<table>
+<tr><th>Name</th><th>Organization</th><th>PPMC Member</th><th>Mentor</th><th>Champion</th><th>IPMC
+</tr>
+<tr><td>Adam Wojtuniak </td><td>Ericsson </td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Alan Cabrera</td><td>LinkedIn</td><td> (/)</td><td> </td><td> </td><td> (/) </td></tr>
+<tr><td>Alan Keane</td><td>Ericsson </td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Alasdair Nottingham</td><td>IBM</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Andrew Osborne</td><td>IBM</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Bartosz Kowalewski</td><td> </td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Bernd Kolb</td><td>SAP</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Bertrand Delacretaz</td><td> </td><td> (/)</td><td>(/) emeritus</td><td> </td><td> (/) </td></tr>
+<tr><td>Carsten Ziegeler</td><td> </td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Chris Wilkinson</td><td>IBM</td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Dan Kulp</td><td>Progress</td><td> (/)</td><td> </td><td> </td><td> (/) </td></tr>
+<tr><td>David Bosschaert</td><td>Red Hat</td><td> (/)</td><td> </td><td> </td><td>	 </td></tr>
+<tr><td>David Jencks</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Davanum Srinivas (Dims)</td><td>IBM</td><td>(/)</td><td>(/)</td><td> </td><td> (/) </td></tr>
+<tr><td>Dimo Stoilov</td><td>SAP</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Emily Jiang</td><td>IBM</td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Eoghan Glynn</td><td>Progress</td><td> (/)</td><td>	</td><td> </td><td> </td></tr>
+<tr><td>Graham Charters</td><td>IBM</td><td> (/)</td><td>	</td><td> </td><td> </td></tr>
+<tr><td>Guillaume Nodet</td><td>Progress</td><td> (/)</td><td>(/)</td><td>(/)</td><td>(/)</td></tr>
+<tr><td>Hiram Chirino</td><td>Progress</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Holly Cummins</td><td>IBM</td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Ian Robinson</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>James Strachan</td><td>Progress</td><td> (/)</td><td>	</td><td> </td><td> (/) </td></tr>
+<tr><td>Jarek Gawor</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> (/) </td></tr>
+<tr><td>Jean-Sebastien Delfino</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Jeremy Hughes</td><td>IBM</td><td> (/) </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Joe Bohn</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Kevan Miller</td><td>IBM</td><td>(/)</td><td>(/)</td><td>(/)</td><td>(/)</td></tr>
+<tr><td>Lei "Rex" Wang</td><td>IBM</td><td> </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Lin Sun</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Kiril Mitov</td><td>SAP</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Mark Nuttall</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Niclas Hedhman</td><td> </td><td>	</td><td> </td><td> </td><td>(/)</td></tr>
+<tr><td>Niklas Gustavsson</td><td> </td><td> (/)</td><td> </td><td> </td><td>	 </td></tr>
+<tr><td>Nikolai Tankov</td><td>SAP</td><td> (/)</td><td> </td><td> </td><td>	 </td></tr>
+<tr><td>Oisin Hurley</td><td>Progress</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Peter Peshev</td><td>SAP</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Raymond Feng</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Rick McGuire</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Roman Roelofsen</td><td>ProSyst</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Sabine Heider</td><td>SAP</td><td> (/) </td><td> </td><td> </td><td> </td></tr>
+<tr><td>Sergey Beryozkin</td><td>Progress</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Stuart McCulloch</td><td> </td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Timothy Ward</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Todor Boev</td><td>ProSyst</td><td> (/)</td><td> </td><td> </td><td>	 </td></tr>
+<tr><td>Valentin Mahrwald</td><td>IBM</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Violeta Georgieva</td><td>SAP</td><td> (/)</td><td> </td><td> </td><td> </td></tr>
+<tr><td>Zoe Slattery</td><td>IBM</td><td> (/)	</td><td> </td><td> </td><td> </td></tr>

Added: incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,20 @@
+h1. Pointers to OSGi specifications
+
+At present, the specifications for Java EE implemented on OSGi are in development and only exist as Requests for Comment within the draft specification for OSGi 4.2.x.
+
+Here are the page numbers for the new draft (version 4) - http://www.osgi.org/download/osgi-4.2-enterprise-early-draft4.pdf.
+
+Web Container Specification version 1.0          page 6
+Transaction Service Specification version 1.0    page 21
+Database Access Specification version 1.0        page 94
+JNDI Service Specification version 1.0           page 147
+
+Here are the pages within the draft version 3 - http://www.osgi.org/download/osgi-4.2-early-draft3.pdf.
+
+OSGi and Web Applications           page 89
+Transactions in OSGi                page 108
+Distributed OSGi                    page 124
+Database Access (JDBC w/in OSGi)    page 188
+Blueprint Service                   page 198
+JMX Control of OSGi                 page 363
+JNDI and OSGi Integration           page 486
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,26 @@
+Title: PointersToOSGiSpecifications
+<a name="PointersToOSGiSpecifications-PointerstoOSGispecifications"></a>
+# Pointers to OSGi specifications
+
+At present, the specifications for Java EE implemented on OSGi are in
+development and only exist as Requests for Comment within the draft
+specification for OSGi 4.2.x.
+
+Here are the page numbers for the new draft (version 4) -
+http://www.osgi.org/download/osgi-4.2-enterprise-early-draft4.pdf.
+
+Web Container Specification version 1.0 	 page 6
+Transaction Service Specification version 1.0	 page 21
+Database Access Specification version 1.0	 page 94
+JNDI Service Specification version 1.0		 page 147
+
+Here are the pages within the draft version 3 -
+http://www.osgi.org/download/osgi-4.2-early-draft3.pdf.
+
+OSGi and Web Applications	    page 89
+Transactions in OSGi		    page 108
+Distributed OSGi		    page 124
+Database Access (JDBC w/in OSGi)    page 188
+Blueprint Service		    page 198
+JMX Control of OSGi		    page 363
+JNDI and OSGi Integration	    page 486

Added: incubator/aries/branches/site/trunk/content/releasenotes.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/releasenotes.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/releasenotes.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/releasenotes.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,50 @@
+h1. Release Notes
+
+h3. New and Noteworthy
+
+Welcome to the 0.2-incubating release. For this release we started running the OSGi Enterprise Compliance tests for relevant components. 
+
+ * [Test Results| http://incubator.apache.org/aries/testresults.html]
+ * [JIRA Release Notes | https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981&styleName=Html&version=12314941]
+
+h3. New Components
+Quiesce.
+The Quiesce component co-ordinates a graceful shutdown across a number of bundles. Quiesce participants respond to quiesce operations and clean up resources. In this release, only the JPA component implements a quiesce participant.
+
+h3. Modules in this release
+
+|| Module || Version || Depends (build)  on Aries module || Version||
+| Application | 0.2-incubating | Util |  0.2-incubating|
+| - | - | Blueprint |  0.2-incubating|
+| - | - | Testsupport |  0.2-incubating|
+| - | - | Web |  0.2-incubating|
+| Blueprint | 0.2-incubating | Util |  0.2-incubating|
+| Eba-maven-plugin | 0.2-incubating | | |
+| JMX | 0.2-incubating |  Util |  0.2-incubating|
+| - | - | Blueprint |  0.2-incubating|
+| JNDI | 0.2-incubating | Util |  0.2-incubating|
+| - | - | Testsupport |  0.2-incubating|
+| JPA | 0.2-incubating |  Util |  0.2-incubating|
+| - | - | Blueprint |  0.2-incubating|
+| - | - | Testsupport |  0.2-incubating|
+| - | - | Quiesce |  0.2-incubating|
+| Quiesce | 0.2-incubating |  Util |  0.2-incubating|
+| - | - | Testsupport |  0.2-incubating|
+|Transaction | 0.2-incubating | Blueprint |  0.2-incubating|
+| - | - | Testsupport |  0.2-incubating|
+|Util| 0.2-incubating |  Testsupport |  0.2-incubating|
+
+
+h3.New samples
+No new samples but we changed the Blog Sample and Aries Trader samples so that no database initialisation is required prior to running the sample.
+
+h3. New Tutorials
+None
+
+h3. API breaking
+None.
+
+h3. Known Issues
+[JIRA query for known issues in the 0.2-incubating release | https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12314569]
+
+h3. Important changes to consider when upgrading

Added: incubator/aries/branches/site/trunk/content/releasenotes.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/releasenotes.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/releasenotes.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/releasenotes.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,67 @@
+Title: ReleaseNotes
+<a name="ReleaseNotes-ReleaseNotes"></a>
+# Release Notes
+
+<a name="ReleaseNotes-NewandNoteworthy"></a>
+### New and Noteworthy
+
+Welcome to the 0.2-incubating release. For this release we started running
+the OSGi Enterprise Compliance tests for relevant components. 
+
+ * [Test Results](-http://incubator.apache.org/aries/testresults.html.html)
+ * [JIRA Release Notes ](-https://issues.apache.org/jira/secure/releasenote.jspa?projectid=12310981&stylename=html&version=12314941.html)
+
+<a name="ReleaseNotes-NewComponents"></a>
+### New Components
+Quiesce.
+The Quiesce component co-ordinates a graceful shutdown across a number of
+bundles. Quiesce participants respond to quiesce operations and clean up
+resources. In this release, only the JPA component implements a quiesce
+participant.
+
+<a name="ReleaseNotes-Modulesinthisrelease"></a>
+### Modules in this release
+
+<table>
+<tr><th> Module </th><th> Version </th><th> Depends (build)  on Aries module </th><th> Version</th></tr>
+<tr><td> Application </td><td> 0.2-incubating </td><td> Util </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Blueprint </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Testsupport </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Web </td><td>  0.2-incubating</td></tr>
+<tr><td> Blueprint </td><td> 0.2-incubating </td><td> Util </td><td>  0.2-incubating</td></tr>
+<tr><td> Eba-maven-plugin </td><td> 0.2-incubating </td><td> </td><td> </td></tr>
+<tr><td> JMX </td><td> 0.2-incubating </td><td>  Util </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Blueprint </td><td>  0.2-incubating</td></tr>
+<tr><td> JNDI </td><td> 0.2-incubating </td><td> Util </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Testsupport </td><td>  0.2-incubating</td></tr>
+<tr><td> JPA </td><td> 0.2-incubating </td><td>  Util </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Blueprint </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Testsupport </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Quiesce </td><td>  0.2-incubating</td></tr>
+<tr><td> Quiesce </td><td> 0.2-incubating </td><td>  Util </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Testsupport </td><td>  0.2-incubating</td></tr>
+<tr><td>Transaction </td><td> 0.2-incubating </td><td> Blueprint </td><td>  0.2-incubating</td></tr>
+<tr><td> - </td><td> - </td><td> Testsupport </td><td>  0.2-incubating</td></tr>
+<tr><td>Util</td><td> 0.2-incubating </td><td>  Testsupport </td><td>	0.2-incubating</td></tr>
+</table>
+
+
+<a name="ReleaseNotes-Newsamples"></a>
+### New samples
+No new samples but we changed the Blog Sample and Aries Trader samples so
+that no database initialisation is required prior to running the sample.
+
+<a name="ReleaseNotes-NewTutorials"></a>
+### New Tutorials
+None
+
+<a name="ReleaseNotes-APIbreaking"></a>
+### API breaking
+None.
+
+<a name="ReleaseNotes-KnownIssues"></a>
+### Known Issues
+[JIRA query for known issues in the 0.2-incubating release ](-https://issues.apache.org/jira/secure/issuenavigator.jspa?mode=hide&requestid=12314569.html)
+
+<a name="ReleaseNotes-Importantchangestoconsiderwhenupgrading"></a>
+### Important changes to consider when upgrading

Added: incubator/aries/branches/site/trunk/content/releasingaries.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/releasingaries.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/releasingaries.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/releasingaries.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,273 @@
+h1. How to do an Aries Release
+
+
+To create a release you will need to create the release artifacts and move then to various places (ultimately the Maven central repository). The Maven commands and general outline of the process looks like this:
+
+!AriesRelease.png!
+
+The picture assumes that you are releasing from a branch rather than from trunk. The full maven commands are not shown - the intention is just to give an indication of which maven commands you will need to use to create assets in different places.
+
+Performing a release is described in detail [here | http://apache.org/dev/publishing-maven-artifacts.html]. This document It covers all the steps listed above so on these pages we will only add things which are specific to the Apache Aries release. Note: the document has not been release and this link will need to be updated when it has.
+
+There are a few steps to the process:
+# Discussion of the release and its content on the aries-dev mailing list.
+# Creating and storing GPG keys
+# Setting up your environment
+# Creating a branch to release from
+# Checking release artifacts on your local system
+# Creating a snapshot release (optional - not really part of the release process, uses mvn deploy)
+# Releasing to a staging repository (uses mvn release:prepare and mvn release:perform)
+# Running a vote
+# Promoting the release artifacts to the Apache release repository
+# Making the release artifacts available from the Aries web pages
+# What to do when people find problems with the release artifacts
+
+The best current documentation for releases is [here | http://apache.org/dev/publishing-maven-artifacts.html] - but this isn't released yet. It covers all the steps listed above so on these pages we will only add things which are specific to the Apache Aries release.
+
+
+h3. Discussion of the release and it's content on the Aries mailing list
+Before starting off the release process it is essential to gain concensus on the aries-dev list that this is the right time for a release and to agree its content. Allow at least a week for this discussion. 
+
+
+h3. Creating and storing GPG keys
+For Aries your GPG key will need to be in this file: https://svn.apache.org/repos/asf/incubator/aries/KEYS (follow the instructions in the file) and checkin
+
+h3. Setting up your environment
+
+Follow the general instructions linked to above. 
+
+h3. Creating a branch to release from
+Although this isn't strictly speaking a necessary step it's pretty useful to do it. Running the commands to create the release can take some time, especially if you have to revert anything. This is much easier if you are working in your own branch and not in trunk where other people may be committing code.
+
+{code}
+svn copy https://svn.apache.org/repos/asf/incubator/aries/trunk \
+           https://svn.apache.org/repos/asf/incubator/aries/branches/0.X-incubating-RCx \
+      -m "Creating a release branch of /aries/trunk."
+{code}
+
+Where '0.X' is the number of the release.
+
+Checkout the new branch, for example, for the 0.2-incubating  release:
+
+{code}
+svn co https://svn.apache.org/repos/asf/incubator/aries/branches/0.2-incubating-RCx aries-rc2-candidate
+{code}
+
+*IMPORTANT* If you are using a branch to release you *must* edit the top level pom.xml for each module to change the SCM references to point to the branch and to to trunk. For example:
+
+{code}
+<connection>scm:svn:http://svn.apache.org/repos/asf/incubator/aries/branches/0.2-incubating-RCx/parent</connection>
+        <developerConnection>scm:svn:https://svn.apache.org/repos/asf/incubator/aries/branches/0.2-incubating-RCx/parent</developerConnection>
+        <url>scm:svn:http://svn.apache.org/repos/asf/incubator/aries/branches/0.2-incubating-RCx/parent</url>
+{code}
+
+The consequence of forgetting this is that the commands that create the release (mvn release:prepare, mvn release:perform) will declare SUCCESS but will not create a staging repository and will add stuff to the snapshot repository :-/.
+
+After taking the branch, change the pom versions in trunk to, say, 0.3-incubating or whatever you want to call the next development version.
+
+h3. Checking release artifacts
+I recommend deleting everything under ...org/apache/aries in your local Maven repo. For linux/Mac users you will find this under ~/.m2/repository/.
+
+Check that the code builds using the usual [sequence | BuildingAries] of commands, but add the following arguments to the 'mvn install' command:
+
+{code}
+mvn install -Papache-release -DcreateChecksum=true
+{code}
+
+This should build and install release artifacts in your local repo. 
+
+Check the [0.1 release|https://repository.apache.org/content/repositories/releases/org/apache/aries/parent/0.1-incubating/] to understand what files should be created.
+
+To perform legal checks, in each subproject, run:
+{code}
+mvn rat:check -fn
+{code}
+
+This will run through the project and its sub projects generating a file called rat.txt in each target directory.
+The 'fn' means it will carry on even if it find a failure. To inspect the failures, the easiest way I've found so far is:
+{code}
+find . -name rat.txt | xargs grep \!\?\?
+{code}
+
+This will pick out the failing file names. Some of the files that rat fails do not require an Apache license, eg MANIFEST.MF, but any *.java or *.js file does need one.
+
+h3. Creating a snapshot release
+TBD. This isn't a necessary step in the release process but should still be documented here.
+
+h3. Creating the release
+
+h5. Creating the release artifacts in a staging repository
+
+Aries is released as a set of modules, not all the modules in Aries are part of the release. Some modules depend on other modules. The release is created by releasing each module separately and in a specific order. It is also desirable to maintain the same IP address for the entire process (the staging repository is associated with your IP address, changing it results in the creation of a second staging repository).
+
+Short summary: Use a wired ether net connection and allow about 4 hours for the next few steps.
+
+From the top level directory in your branch run:
+{code}
+mvn clean
+{code}
+
+Then, change directory to 'parent'. It is necessary to release parent first because everything else depends on it. Run the following commands:
+
+{code}
+mvn install -Papache-release
+mvn release:prepare -Papache-release
+mvn release:perform -Papache-release
+{code}
+
+*Note* The prepare step will make some assumptions about the version of the development steam that is left after the release has been made. When releasing from a branch it may not be a good idea to accept the default for this, it will very likely conflict with the development version in use in trunk.
+
+The install command is required to make sure that you have a copy of the parent in your local repository - it's required for releasing the eba-maven-plugin.
+
+This _should _ start to put release artifacts into an Apache [staging repository | https://repository.apache.org/index.html#view-repositories;staging]. You will need to log in to see it.
+If nothing appears in a staging repo you should stop here and work out why :-). If you have made a mistake it's quite easy to revert. The release commands make and commit changes to the project's pom.xml files and they create a tag in SVN. To revert the changes you will need to revert the pom.xml files and delete the tag from svn.
+
+If you are in Europe the mvn release:prepare command almost always fails at the last step, with a message like:
+
+{code}
+[ERROR] BUILD FAILURE
+[INFO] ------------------------------------------------------------------------
+[INFO] Unable to tag SCM
+Provider message:
+The svn tag command failed.
+Command output:
+svn: No such revision 936951
+{code}
+This is due to the SVN mirroring in place between Europe and the master in the US. When you make a commit, it isn't immediately available in Europe to svn up to. Just wait 10 secs and repeat the mvn release:prepare command for it to restart where it left off.
+
+
+The next step is to release the eba-maven-plugin.
+{code}
+cd ../eba/maven-plugin
+mvn versions:update-parent
+mvn versions:use-releases
+svn commit -m "updated to latest releases"
+mvn release:prepare -Papache-release
+mvn release:perform -Papache-release
+{code}
+
+Then for each project, in the order given below:
+
+testsupport
+util
+blueprint 
+jndi
+transaction
+web
+application
+jmx
+quiesce
+jpa
+samples *See Note 1 below*
+
+Run the following commands:
+{code}
+mvn versions:update-parent
+mvn versions:use-releases
+svn commit -m "updated to latest releases"
+mvn release:prepare -Papache-release -DpreparationGoals="clean install" *See Note 2 below*
+mvn release:perform -Papache-release
+{code}
+
+  * Note 1: when doing mvn versions:* actions in samples, you must also manually change the version properties that are hard coded in the top level pom.xml. The only '-SNAPSHOT' you should have left in samples/pom.xml is the version element for the module itself.
+  * Note 2: -DpreparationGoals="clean install"  is needed for all modules that have sub modules with dependencies between them, in practice this is most modules.
+
+h5. Closing the staging repository
+After checking that the staging repository contains the artifacts that you expect you should close the staging repository. This will make it available so that people can check the release.
+
+h3. Running the vote(s)
+
+Two votes are required for an incubator release. The first from the aries-dev@incubator.apache.org list, the second from general@incubator.apache.org. These run consecutively, 72 hours is required for each vote.
+
+After all the modules are present in the staging repository you will need to close the repository so that reviewers can access the modules. At this point you should write two notes to the aries-dev mailing list.
+
+ * Subject \[VOTE\] Apache Aries (Incubating) version 0.X-incubating release candidate 02
+
+The the source archive files should be explicitly called out by release manager in any release vote. From an Apache legal standpoint, this is what the project is "releasing" and what the community should be voting on. In this [sample note| http://people.apache.org/~zoe/devlistvote.txt], there is a link to each modules' source*.zip file.
+
+
+ * Subject \[DISCUSS\] Apache Aries (Incubating) version 0.X-incubating release candidate 0X
+
+The content should just indicate that the note starts a thread to discuss the Aries 0.X-incubating release.
+
+
+After 72 hours, if no problems have been found in the release artifacts, the aries-dev vote can be summarised and closed. Note that at least three +1 votes from Aries IPMC members are required. 
+
+After closing the vote on the aries-dev list, the second vote (on the general@) can be started. Here is a [sample note|http://people.apache.org/~zoe/generallistvote.txt], the subject of the note is \[VOTE\]Approval to release Apache Aries (Incubating) version 0.X-incubating
+
+
+After another 72 hours, assuming there are no objections, this vote can also be summarised and closed.
+
+h3. Promoting the release artifacts
+From the [Nexus pages|https://repository.apache.org/index.html#stagingRepositories], select the staging repository and select 'release' from the top menu. This moves the release artifacts into an Apache releases repository, from there they will be automatically moved to the Maven repository.
+
+h3. Making the release artifacts available from the Aries web pages. 
+Anything that is to be downloaded must be put in /www/www.apache.org/dist/incubator/aries on minotaur. The distributions are archived here /www/archive.apache.org/dist/incubator/aries.
+
+First, delete the previous distribution from the distribution directory. Download the release artifacts using a script like [this| http://people.apache.org/~zoe/release-0.2 ]. Next, update the Aries Downloads pages to refer to the new artifacts.
+
+
+
+h3. What to do when people find problems with the release
+ * Cancel the vote \[CANCELLED\]\[VOTE\]
+ * Clean up, fix and re-release.
+The good news here is that it isn't necessarily essential to re-release every module. 
+
+
+h3. Cleaning up, fixing and re-releasing
+
+
+The release process makes changes to project poms and adds a tag in svn. The first step is to revert the changes to the poms in the problem modules. The following steps work on a *ix like platform:
+
+Determine which revision you want to go back to (eg XXXXX)
+{code}
+svn up -r XXXXXX
+find . -name pom.xml | xargs -I {} mv {} {}_old
+svn up
+find . -name pom.xml | xargs -I {} mv {}_old {}
+svn status #Check what you have changed!
+svn commit -m "reverting release changes"
+{code}
+
+Next - delete the tag relating to the module from SVN
+
+Finally - delete the folder from the staging repository (this seems to take several attempts and a very long time to achieve)
+
+Make the fixes that you need to in the project, commit them and work through the release process again. 
+
+In some cases you may also want to merge from trunk into the release branch. The syntax to do this is:
+{code}
+svn merge -c ZZZZZZ https://svn.apache.org/repos/asf/incubator/aries/trunk
+{code}
+Where ZZZZZZ is the revision associated with the fix.
+Note that you will be creating a new staging repository. The commands are repeated here for convenience:
+
+{code}
+mvn versions:update-parent
+mvn versions:use-releases
+svn commit -m "<version> RC<#>: updated to latest releases"
+mvn release:prepare -Papache-release -DpreparationGoals="clean install"
+mvn release:perform -Papache-release
+{code}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+



Mime
View raw message