Recent changes to Source

Discussion for Source page

ssjong — Fri, 25 Nov 2016 03:01:40 -0000

The repo is private....it is not read only for everyone...

Discussion for Source page

Pedro Mendes — Fri, 29 May 2015 11:04:57 -0000

Hi,
It's said that the svn repo has read-only rights but I'm still asked for an account when I try to navigate in the repo pages or when I try to check the, a tag or branch.

How do I get the required permissions?

WikiPage Source modified by Dave McAllister

Dave McAllister — Wed, 14 Nov 2012 22:59:53 -0000

--- v4
+++ v5
@@ -1,12 +1,3 @@
-
-
-  
-
-
-
-
-
-
 # BlazeDS Source
 
 BlazeDS is one of several open-source projects in a Subversion repository hosted by Adobe. Subversion is an open-source revision control system used for many open-source projects. If you haven't used it before, please see the official documentation.

WikiPage Source modified by pallab jyotee hazarika

pallab jyotee hazarika — Sat, 03 Mar 2012 07:24:14 -0000

--- v3 
+++ v4 
@@ -39,33 +39,32 @@
 
 _NOTE: The Subversion repository should only be used if you want to be on the bleeding-edge of the development effort. The code contained in them may fail to work, or it may even eat your hard drive._
 
-When you access the repository with a Subversion client, the BlazeDS project is at the URL http://opensource.adobe.com/svn/opensource/blazeds.
-
+When you access the repository with a Subversion client, the BlazeDS project is at the URL https://sourceforge.net/adobe/blazeds/.
+
 To get the source code, do a "checkout" of the trunk or some branch or tag into a local directory on your machine. For example, to get the code in the trunk, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/trunk. Using the command-line client, you would execute
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/trunk 
     
 
 To get the code that was used to build the BlazeDS 4 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0 
     
 
 To get the code that was used to build the BlazeDS 3 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0 
     
 
 **Warning**: You probably _don't_ want to check out the entire `blazeds` directory, as you'll get every branch and tag, each of which is comparable in size to the trunk.
 
 ## Access rights
 
 Everyone has read-only access to the BlazeDS project. If you want to contribute to the BlazeDS project, refer to the BlazeDS page on [Submitting a Patch](Submitting%20a%20Patch).
 
 ## Change notifications
 
 If you'd like to keep up-to-date on changes to the BlazeDS project, you may subscribe to the Commits forum.
-

WikiPage Source modified by pallab jyotee hazarika

pallab jyotee hazarika — Sat, 03 Mar 2012 07:21:02 -0000

--- v2 
+++ v3 
@@ -1,73 +1,71 @@
-
 
 
   
 
 
 
 
 
 
 # BlazeDS Source
 
 BlazeDS is one of several open-source projects in a Subversion repository hosted by Adobe. Subversion is an open-source revision control system used for many open-source projects. If you haven't used it before, please see the official documentation.
 
 ## View the BlazeDS Source Tree
 
 If you just wish to browse around the BlazeDS source tree, go straight to the public repository [here](http://opensource.adobe.com/svn/opensource/blazeds/). 
 
 #### BlazeDS Source Tree Organization
 
 Within the project are directories named `trunk`, `branches`, and `tags`, as is standard for Subversion projects.
 
 The **trunk** is generally work-in-progress on the version under current development. The trunk should build and pass basic tests but may be unstable and unsuitable for use.
 
 **Branches** are created when projects need to stabilize code for a release. The BlazeDS 4 code may be found in branches/4.x and BlazeDS 3 code may be found in branches/3.x.
 
 **Tags** record the code that shipped as a specific release, or other milestones in a project. The code which shipped as the 4.0 release has been tagged as tags/4.0.0.
 
 ## Access the BlazeDS Source
 
 Most users of the source code probably don't need to have day to day access to the source code as it changes. For these users we provide a zip file of the latest stable release. 
 
-  * To download a zip file of the source of the latest stable release, go [here](http://opensource.adobe.com/wiki/display/blazeds/download%2Bblazeds%2B4)
+  * To download a zip file of the source of the latest stable release, go [here](https://sourceforge.net/adobe/blazeds/wiki/download%20blazeds%204/)
 
 \\
 
 #### Checking out Source Code
 
 If you feel that you need access to the source tree to get a local copy of the latest and greatest code, you will need a Subversion client. The BlazeDS team has had good experience with TortoiseSVN on Windows and SmartSVN on Macintosh, both of which are GUI clients. (This is not an official endorsement of these products by Adobe.) Of course, you can use whatever client you prefer, including Subversion's official command-line tool `svn`.
 
 _NOTE: The Subversion repository should only be used if you want to be on the bleeding-edge of the development effort. The code contained in them may fail to work, or it may even eat your hard drive._
 
 When you access the repository with a Subversion client, the BlazeDS project is at the URL http://opensource.adobe.com/svn/opensource/blazeds.
 
 To get the source code, do a "checkout" of the trunk or some branch or tag into a local directory on your machine. For example, to get the code in the trunk, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/trunk. Using the command-line client, you would execute
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/trunk 
     
 
 To get the code that was used to build the BlazeDS 4 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0 
     
 
 To get the code that was used to build the BlazeDS 3 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0 
     
 
 **Warning**: You probably _don't_ want to check out the entire `blazeds` directory, as you'll get every branch and tag, each of which is comparable in size to the trunk.
 
 ## Access rights
 
 Everyone has read-only access to the BlazeDS project. If you want to contribute to the BlazeDS project, refer to the BlazeDS page on [Submitting a Patch](Submitting%20a%20Patch).
 
 ## Change notifications
 
 If you'd like to keep up-to-date on changes to the BlazeDS project, you may subscribe to the Commits forum.
-

WikiPage Source modified by pallab jyotee hazarika

pallab jyotee hazarika — Sat, 03 Mar 2012 07:18:38 -0000

--- v1 
+++ v2 
@@ -1,84 +1,73 @@
 
-
 
 
   
 
 
 
 
 
 
 # BlazeDS Source
 
 BlazeDS is one of several open-source projects in a Subversion repository hosted by Adobe. Subversion is an open-source revision control system used for many open-source projects. If you haven't used it before, please see the official documentation.
 
 ## View the BlazeDS Source Tree
 
 If you just wish to browse around the BlazeDS source tree, go straight to the public repository [here](http://opensource.adobe.com/svn/opensource/blazeds/). 
 
 #### BlazeDS Source Tree Organization
 
 Within the project are directories named `trunk`, `branches`, and `tags`, as is standard for Subversion projects.
 
 The **trunk** is generally work-in-progress on the version under current development. The trunk should build and pass basic tests but may be unstable and unsuitable for use.
 
 **Branches** are created when projects need to stabilize code for a release. The BlazeDS 4 code may be found in branches/4.x and BlazeDS 3 code may be found in branches/3.x.
 
 **Tags** record the code that shipped as a specific release, or other milestones in a project. The code which shipped as the 4.0 release has been tagged as tags/4.0.0.
 
 ## Access the BlazeDS Source
 
 Most users of the source code probably don't need to have day to day access to the source code as it changes. For these users we provide a zip file of the latest stable release. 
 
   * To download a zip file of the source of the latest stable release, go [here](http://opensource.adobe.com/wiki/display/blazeds/download%2Bblazeds%2B4)
 
 \\
 
 #### Checking out Source Code
 
 If you feel that you need access to the source tree to get a local copy of the latest and greatest code, you will need a Subversion client. The BlazeDS team has had good experience with TortoiseSVN on Windows and SmartSVN on Macintosh, both of which are GUI clients. (This is not an official endorsement of these products by Adobe.) Of course, you can use whatever client you prefer, including Subversion's official command-line tool `svn`.
 
 _NOTE: The Subversion repository should only be used if you want to be on the bleeding-edge of the development effort. The code contained in them may fail to work, or it may even eat your hard drive._
 
 When you access the repository with a Subversion client, the BlazeDS project is at the URL http://opensource.adobe.com/svn/opensource/blazeds.
 
 To get the source code, do a "checkout" of the trunk or some branch or tag into a local directory on your machine. For example, to get the code in the trunk, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/trunk. Using the command-line client, you would execute
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/trunk 
     
 
 To get the code that was used to build the BlazeDS 4 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0 
     
 
 To get the code that was used to build the BlazeDS 3 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0:
 
 
     svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0 
     
 
 **Warning**: You probably _don't_ want to check out the entire `blazeds` directory, as you'll get every branch and tag, each of which is comparable in size to the trunk.
 
 ## Access rights
 
 Everyone has read-only access to the BlazeDS project. If you want to contribute to the BlazeDS project, refer to the BlazeDS page on [Submitting a Patch](Submitting%20a%20Patch).
 
 ## Change notifications
 
 If you'd like to keep up-to-date on changes to the BlazeDS project, you may subscribe to the Commits forum.
-
-
-
-
-
-  
-[[ include ref='blazeds_rightnav' ]]  
-
-
-

WikiPage Source modified by Cory Johns

Cory Johns — Fri, 10 Feb 2012 21:22:05 -0000

# BlazeDS Source BlazeDS is one of several open-source projects in a Subversion repository hosted by Adobe. Subversion is an open-source revision control system used for many open-source projects. If you haven't used it before, please see the official documentation. ## View the BlazeDS Source Tree If you just wish to browse around the BlazeDS source tree, go straight to the public repository [here](http://opensource.adobe.com/svn/opensource/blazeds/). #### BlazeDS Source Tree Organization Within the project are directories named `trunk`, `branches`, and `tags`, as is standard for Subversion projects. The **trunk** is generally work-in-progress on the version under current development. The trunk should build and pass basic tests but may be unstable and unsuitable for use. **Branches** are created when projects need to stabilize code for a release. The BlazeDS 4 code may be found in branches/4.x and BlazeDS 3 code may be found in branches/3.x. **Tags** record the code that shipped as a specific release, or other milestones in a project. The code which shipped as the 4.0 release has been tagged as tags/4.0.0. ## Access the BlazeDS Source Most users of the source code probably don't need to have day to day access to the source code as it changes. For these users we provide a zip file of the latest stable release. * To download a zip file of the source of the latest stable release, go [here](http://opensource.adobe.com/wiki/display/blazeds/download%2Bblazeds%2B4) \\ #### Checking out Source Code If you feel that you need access to the source tree to get a local copy of the latest and greatest code, you will need a Subversion client. The BlazeDS team has had good experience with TortoiseSVN on Windows and SmartSVN on Macintosh, both of which are GUI clients. (This is not an official endorsement of these products by Adobe.) Of course, you can use whatever client you prefer, including Subversion's official command-line tool `svn`. _NOTE: The Subversion repository should only be used if you want to be on the bleeding-edge of the development effort. The code contained in them may fail to work, or it may even eat your hard drive._ When you access the repository with a Subversion client, the BlazeDS project is at the URL http://opensource.adobe.com/svn/opensource/blazeds. To get the source code, do a "checkout" of the trunk or some branch or tag into a local directory on your machine. For example, to get the code in the trunk, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/trunk. Using the command-line client, you would execute svn checkout http://opensource.adobe.com/svn/opensource/blazeds/trunk To get the code that was used to build the BlazeDS 4 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0: svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/4.0.0 To get the code that was used to build the BlazeDS 3 release, checkout from the URL http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0: svn checkout http://opensource.adobe.com/svn/opensource/blazeds/tags/3.0.0 **Warning**: You probably _don't_ want to check out the entire `blazeds` directory, as you'll get every branch and tag, each of which is comparable in size to the trunk. ## Access rights Everyone has read-only access to the BlazeDS project. If you want to contribute to the BlazeDS project, refer to the BlazeDS page on [Submitting a Patch](Submitting%20a%20Patch). ## Change notifications If you'd like to keep up-to-date on changes to the BlazeDS project, you may subscribe to the Commits forum.

[[ include ref='blazeds_rightnav' ]]