You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by dk...@apache.org on 2013/05/29 15:45:55 UTC

svn commit: r1487486 - /sling/site/trunk/content/documentation/development/release-management.mdtext

Author: dklco
Date: Wed May 29 13:45:54 2013
New Revision: 1487486

URL: http://svn.apache.org/r1487486
Log:
Fixing Appendix C of the release management page

Modified:
    sling/site/trunk/content/documentation/development/release-management.mdtext

Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1487486&r1=1487485&r2=1487486&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Wed May 29 13:45:54 2013
@@ -289,75 +289,60 @@ When running the `mvn release:prepare` c
     svn: Commit failed (details follow):
     svn: MKACTIVITY of '/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c': authorization failed (https://svn.apache.org){code}
     
-    This is due to a bug in Subversion on the Mac, as described by Brett Porter in his [blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/]. He proposes putting an "svn" script at the head of your path to fix the issue.
+This is due to a bug in Subversion on the Mac, as described by Brett Porter in his [blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/]. He proposes putting an "svn" script at the head of your path to fix the issue.
     
+## Appendix C: Deploy bundles on the Sling OBR
     
+We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles. This repository is maintained as part of the Apache Sling site and is available at [http://sling.apache.org/obr/sling.xml]. The source for this page is maintained in the SVN repository below the _site_, that is at [http://svn.apache.org/repos/asf/sling/site/]. To update the Sling OBR repository you must be an Apache Sling Committer since this requires SVN write access.
     
-    h2. Appendix C: Deploy bundles on the Sling OBR
-    
-    We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles. This repository is maintained as part of the Apache Sling site and is available at [http://sling.apache.org/obr/sling.xml]. The source for this page is maintained in the SVN repository below the _site_, that is at [http://svn.apache.org/repos/asf/sling/site/]. To update the Sling OBR repository you must be an Apache Sling Committer since this requires SVN write access.
-    
-    To update the OBR you may use the Apache Felix Maven Bundle Plugin which prepares the bundle descriptor to be added to the OBR file. Follow these steps to update the OBR:
-    
-    *1. Checkout or update the Site Source*
+To update the OBR you may use the Apache Felix Maven Bundle Plugin which prepares the bundle descriptor to be added to the OBR file. Follow these steps to update the OBR:
     
+1. Checkout or update the Site Source
+   
+    $ svn checkout https://svn.apache.org/repos/asf/sling/site 
 
-$ svn checkout https://svn.apache.org/repos/asf/sling/site
-
-    
-    Note, that you have to checkout the site using the {{https}} URL, otherwise you will not be able to commit the changes later.
+Note, that you have to checkout the site using the {{https}} URL, otherwise you will not be able to commit the changes later.
     
-    *2. Deploy the Descriptor*
+2. Deploy the Descriptor
     
     To deploy the project descriptor, checkout the tag of the bundle to deploy and run maven
     
 
-$ svn checkout http://svn.apache.org/repos/asf/sling/tags/the*module*tag
-$ mvn clean install \
-    org.apache.felix:maven-bundle-plugin:deploy \
-    -DprefixUrl=http://repo1.maven.org/maven2 \
-    -DremoteOBR=sling.xml \
-    -DaltDeploymentRepository=apache.releases::default::file:///path*to*site_checkout/obr
+    $ svn checkout http://svn.apache.org/repos/asf/sling/tags/the*module*tag
+    $ mvn clean install \
+        org.apache.felix:maven-bundle-plugin:deploy \
+        -DprefixUrl=http://repo1.maven.org/maven2 \
+        -DremoteOBR=sling.xml \
+        -DaltDeploymentRepository=apache.releases::default::file:///path*to*site_checkout/obr
 
+This generates the bundle descriptor and adds it to the {{sling.xml}} file of your site checkout.
     
-    This generates the bundle descriptor and adds it to the {{sling.xml}} file of your site checkout.
+2a. Variant: Refer to Maven Repository
     
-    
-    *2a. Variant: Refer to Maven Repository*
-    
-    Instead of checking out and building the project locally, you may also use the {{deploy-file}} goal of the Maven Bundle Plugin:
-    
-
-$ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar
-$ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.pom
-$ mvn org.apache.felix:maven-bundle-plugin:deploy-file \
-    -Dfile=the*module-version.jar -DpomFile=the*module-version.pom \
-    -DbundleUrl=http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar \
-    -Durl=file:///path*to*site_checkout/obr \
-    -DprefixUrl=http://repo1.maven.org/maven2 \
-    -DremoteOBR=sling.xml
-$ rm the*module-version.jar the*module-version.pom
+Instead of checking out and building the project locally, you may also use the {{deploy-file}} goal of the Maven Bundle Plugin:
 
-    
-    
-    *3. Commite the Site Changes*
-    
-    In the Site checkout folder commit the changes to the {{obr/sling.xml}} files (you may also review the changes using the {{svn diff}} command).
-    
+    $ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar
+    $ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.pom
+    $ mvn org.apache.felix:maven-bundle-plugin:deploy-file \
+        -Dfile=the*module-version.jar -DpomFile=the*module-version.pom \
+        -DbundleUrl=http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar \
+        -Durl=file:///path*to*site_checkout/obr \
+        -DprefixUrl=http://repo1.maven.org/maven2 \
+        -DremoteOBR=sling.xml
+    $ rm the*module-version.jar the*module-version.pom
 
-$ svn commit -m"Add Bundle ABC Version X.Y.Z" obr/sling.xml
+3. Commite the Site Changes
 
+In the Site checkout folder commit the changes to the {{obr/sling.xml}} files (you may also review the changes using the {{svn diff}} command).
     
-    
-    *4. Update the Site on* {{{*}people.apache.org{*}}}
-    
-    After committing the changes, you have to update the site source, which is getting mirrored to the web servers on {{people.apache.org}}
-    
-
-$ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
+    $ svn commit -m"Add Bundle ABC Version X.Y.Z" obr/sling.xml
 
+4. Update the Site on* {{{*}people.apache.org{*}}
+    
+After committing the changes, you have to update the site source, which is getting mirrored to the web servers on {{people.apache.org}}
     
-    After updating the site source it will generally take an hour or two until the changes are visible on the web.
+    $ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
 
+After updating the site source it will generally take an hour or two until the changes are visible on the web.
 
-  [1]: https://dist.apache.org/repos/dist/release/sling/
\ No newline at end of file
+[1]: https://dist.apache.org/repos/dist/release/sling/
\ No newline at end of file