Remove references to RIAForge.

seancorfield · seancorfield · commit 134035dc9c6e · 2016-08-29T17:50:47.000-07:00
Point to GitHub releases page (mostly).
diff --git a/source/_posts/2010-09-21-cfmljure-mailing-list.markdown b/source/_posts/2010-09-21-cfmljure-mailing-list.markdown
@@ -9,6 +9,4 @@ I mentioned it in passing in one of my early posts about using Clojure from CFML
 
 I'm planning to add a couple of more involved examples to the project repo, one of which will use FW/1 and have the entire Model built in Clojure with the View-Controller portion written in CFML / cfscript - and I'm also planning to create a simple ready-to-run Jetty-based package so folks can simply download cfmljure and try it out without needing to worry about installing anything.
 
-You can always get the [latest version of cfmljure from RIAForge](http://cfmljure.riaforge.org/)!
-
- 
+You can always get the [latest version of cfmljure from GitHub](https://github.com/framework-one/cfmljure/releases)!
diff --git a/source/_posts/2010-10-18-fw1-1-2-available.markdown b/source/_posts/2010-10-18-fw1-1-2-available.markdown
@@ -5,6 +5,6 @@ date: 2010-10-18 18:59:11 -0700
 comments: true
 categories: [releases, fw1]
 ---
-The official 1.2 release of Framework One - FW/1 - has just been tagged and published on github. You can [download it from RIAForge](http://fw1.riaforge.org/).
+The official 1.2 release of Framework One - FW/1 - has just been tagged and published on github. You can [download it from GitHub](https://github.com/framework-one/fw1/releases).
 
 Release Candidate 2 had been out for about a month with no issues reported. A few small enhancements were made since RC2. You can see the [list of commits](http://github.com/seancorfield/fw1/commits/master) here, on github.
diff --git a/source/_posts/2011-12-18-fw1-2-0-released.markdown b/source/_posts/2011-12-18-fw1-2-0-released.markdown
@@ -5,4 +5,4 @@ date: 2011-12-18 18:51:18 -0700
 comments: true
 categories: [releases, fw1]
 ---
-After a long period of testing out in the wild FW/1 2.0 reached RC2 back in October and no further bugs have been reported. Only documentation remained and that has now been completed. FW/1 2.0 is gold and can be downloaded from [FW/1's RIAForge site](http://fw1.riaforge.org/). Happy Holidays!
+After a long period of testing out in the wild FW/1 2.0 reached RC2 back in October and no further bugs have been reported. Only documentation remained and that has now been completed. FW/1 2.0 is gold and can be downloaded from [FW/1's GitHub Releases page](https://github.com/framework-one/fw1/releases). Happy Holidays!
diff --git a/source/_posts/2013-01-05-fw1-version-2-1-released.markdown b/source/_posts/2013-01-05-fw1-version-2-1-released.markdown
@@ -27,6 +27,4 @@ In summary then, version 2.1 contains:
 * `request` scope cleanup (and removal of several `request` variables that had previously been marked as deprecated.
 * Lots of small improvements to the robustness of application startup in the face of user code problems, making it easier to debug those problems, and several enhancements to error handling in general.
 
-You can [download FW/1 2.1 at RIAForge](http://fw1.riaforge.org/).
-
- 
+You can [download FW/1 2.1 at GitHub](https://github.com/framework-one/fw1/releases).
diff --git a/source/_posts/2013-05-07-where-can-i-download-old-versions-of-fw1.markdown b/source/_posts/2013-05-07-where-can-i-download-old-versions-of-fw1.markdown
@@ -9,4 +9,4 @@ I've been asked this several times recently so I figured it was worth a blog pos
 
 Okay, so why haven't I blogged about this before? Truth be told, I thought it was "obvious" how to find specific legacy releases on any Github project. Apparently, it is not obvious for everyone so it is worth blogging about. Every properly managed project on Github tags every official release so that all past releases can be found on the 'tags' page. You can see [FW/1's 'tags' page](https://github.com/framework-one/fw1/tags) where you can find every release since 1.0. Unfortunately, my choice of naming for tags has not always been consistent and I forgot the 'v' prefix for a while around the release of 2.0. Oops. Unfortunately the typical naming convention for prereleases tends to sort them above their gold release versions - see [Clojure's core.logic library's tags](https://github.com/clojure/core.logic/tags) for a more striking example. At least Github provides an easy mechanism for provided tagged archive releases.
 
-It's probably worth pointing out that downloading FW/1 directly from the [FW/1 RIAForge project page](http://fw1.riaforge.org/) will give you the latest stable release which is currently 2.1.1. That's because it downloads a ZIP file of the "master" branch from the Github site. All development is performed on the "develop" branch. The only time the RIAForge site will slip you something different is when a new release is in the Release Candidate stage and I update the RIAForge page to download a ZIP file of the "develop" branch - and I update the page to clearly state that! - and this is to increase adoption of the new release and help flush out any remaining bugs that haven't been caught during the alpha and beta testing phases.
+It's probably worth pointing out that downloading FW/1 directly from the [FW/1 GitHub project page](https://github.com/framework-one/fw1) will give you the latest stable release which is currently 2.1.1. That's because it downloads a ZIP file of the "master" branch from the Github site. All development is performed on the "develop" branch.
diff --git a/source/_posts/2013-12-18-fw1-2-2-released.markdown b/source/_posts/2013-12-18-fw1-2-2-released.markdown
@@ -5,7 +5,7 @@ date: 2013-12-18 23:34:03 -0700
 comments: true
 categories: [releases, fw1]
 ---
-Framework One version 2.2 is now available for production use! You can download it from the [Framework One page on RIAForge](http://fw1.riaforge.org/). This includes one bug fix over RC2 (interaction between `renderData()` and trace output).<!-- more -->
+Framework One version 2.2 is now available for production use! You can download it from the [Framework One releases page on GitHub](https://github.com/framework-one/fw1/releases). This includes one bug fix over RC2 (interaction between `renderData()` and trace output).<!-- more -->
 
 The main focus of the 2.2 release is improved support for REST APIs, through the addition of `renderData()` to simplify returning JSON, XML and plain text results to the caller, as well as more sophisticated route handling via "resource packs" which let you define a family of related routes for a given resource type, using a shorthand notation. For more information, see this [blog post about the latest FW/1 release and the roadmap](/blog/2013/11/03/fw1-releases-and-roadmap/).
 
diff --git a/source/_posts/2014-05-25-fw1-2-5-is-released.markdown b/source/_posts/2014-05-25-fw1-2-5-is-released.markdown
@@ -7,7 +7,7 @@ categories: [releases, fw1, di1]
 ---
 This is a migration release to pave the way for breaking changes in Release 3.0. All examples have been updated to latest best practices and now use cfcscript exclusively. Examples use DI/1 0.5.0 to manage all beans and services (as `framework.ioc`), and no longer rely on start/end actions or the `service()` method.<!-- more -->
 
-As always, FW/1 can be downloaded from the [FW/1 page on RIAForge](http://fw1.riaforge.org). Release 2.5 is now the latest stable release of this framework, as it approaches its fifth birthday!
+As always, FW/1 can be downloaded from the [FW/1 GitHub Releases page](https://github.com/framework-one/fw1/releases). Release 2.5 is now the latest stable release of this framework, as it approaches its fifth birthday!
 
 For a full list of all tickets closed in Release 2.5: https://github.com/framework-one/fw1/issues?milestone=14&page=1&state=closed
 
@@ -27,4 +27,3 @@ but, like the other two options, defaults to disallowing the deprecated feature.
 If you enable these deprecated features, you will no longer get exceptions using them, but you will see deprecation warnings in your application server's console log. This is to remind you to update your code in preparation for 3.0 later this year!
 
 _Please note that Release 3.0 will completely remove these backward compatibility options - and the associated deprecated features. In addition, `org.corfield.framework` will move to `framework.one` in Release 3.0, alongside `framework.ioc`._
-
diff --git a/source/_posts/2015-01-24-fw1-3-0-rc-1-available.markdown b/source/_posts/2015-01-24-fw1-3-0-rc-1-available.markdown
@@ -17,5 +17,3 @@ In addition, AOP/1 is no longer bundled with FW/1. It's not ready for primetime
 As part of the preparation for RC 1, all of the documentation has been reviewed and updated and DI/1's documentation is now [part of the main documentation site](http://framework-one.github.io/documentation/using-di-one.html). Big thanks go to Nando Breiter for bringing that across from the old wiki in the standalone DI/1 repo. Code contributors to RC 1 include: John Berquist, Ryan Guill, Cameron Childress. Thank you!
 
 At this point, only bug fixes will be considered before FW/1 3.0 goes "gold" and given the long period of testing so far on Beta 1, that final release shouldn't be too far away.
-
-Oh, and if you go to [FW/1's page on RIAForge](http://fw1.riaforge.org), you'll see that 3.0 RC 1 is the default download now, instead of 2.5.
diff --git a/source/_posts/2015-07-07-fw1-3-1-rc-2.markdown b/source/_posts/2015-07-07-fw1-3-1-rc-2.markdown
@@ -17,7 +17,7 @@ For a complete list of changes since 3.0:
 * [Issues Closed](https://github.com/framework-one/fw1/issues?q=is%3Aissue+is%3Aclosed+milestone%3A3.1)
 * [Pull Requests Merged](https://github.com/framework-one/fw1/pulls?q=is%3Apr+is%3Aclosed+milestone%3A3.1)
 
-At this point, release 3.1 should be considered "production ready" and only critical bug fixes will be included between now and the "gold" release. It is the default download on RIAForge and will be merged to master tomorrow in preparation for the final release at the weekend.
+At this point, release 3.1 should be considered "production ready" and only critical bug fixes will be included between now and the "gold" release. It will be merged to master tomorrow in preparation for the final release at the weekend.
 
 As noted before, release 3.5 will follow fairly quickly after that, with a focus on language integration, bringing
 automatic support for Clojure code in the Model and Controllers, as well as first class support for the Lucee Language in the Model, the Views, and the Controllers.
diff --git a/source/_posts/2015-10-06-fw1-3-5-0-rc-2.markdown b/source/_posts/2015-10-06-fw1-3-5-0-rc-2.markdown
@@ -7,7 +7,7 @@ categories: [releases, fw1, di1, aop1, clojure]
 ---
 The [second Release Candidate of FW/1 3.5.0](https://github.com/framework-one/fw1/releases/tag/v3.5.0-rc2) is available for testing.
 
-This Release Candidate contains a few bug fixes discovered since Release Candidate 1 and is now the [default download from FW/1's RIAForge page](http://fw1.riaforge.org).
+This Release Candidate contains a few bug fixes discovered since Release Candidate 1.
 I consider this stable enough to evaluate for production usage at this point -- I expect this RC to be the Gold Release unless end user testing uncovers a showstopping issue in the next week or two!
 
 You can read the [full list of changes since 3.1](https://github.com/framework-one/fw1/issues?q=is%3Aissue+milestone%3A3.5+is%3Aclosed) on GitHub, along with
diff --git a/source/documentation/4.0/index.markdown b/source/documentation/4.0/index.markdown
@@ -35,17 +35,17 @@ The FW/1 documentation is copyright (c) 2009-2015 Sean Corfield and is made avai
 
 There are two options by which to install FW/1: either download it, or install it via CommandBox.
 
-**Download from Github or RIAForge**
+**Download from Github**
 
-FW/1 can be downloaded directly from the **releases** page on [Github](https://github.com/framework-one/fw1) or from [RIAForge](http://fw1.riaforge.org/). Both paths will lead you to the same [page which lists all the releases](https://github.com/framework-one/fw1/releases), with the latest stable release and pre-release versions listed first.
+FW/1 can be downloaded directly from the **releases** page on [Github](https://github.com/framework-one/fw1). Both paths will lead you to the same [page which lists all the releases](https://github.com/framework-one/fw1/releases), with the latest stable release and pre-release versions listed first.
 
 When you download FW/1 (or check it out from Github), it's a complete web application. **The `framework` folder should either be copied to your webroot (the simplest way to get started) or else made accessible via a mapping for `/framework`.** Since `Application.cfc` extends `framework.one`, you have to add that mapping in your CFML admin - you cannot use a per-application mapping. _In release 3.5 there is a way to avoid the mapping and extending `framework.one` which we'll cover in the [Developing Applications Guide](developing-applications.html#alternative-application-structure)._
 
 **Download with CommandBox**
 
 FW/1 may also be installed via [CommandBox](https://www.ortussolutions.com/products/commandbox). From your command prompt, you can easily install FW/1 by entering `box install fw1` and the latest stable version will be installed to your current working directory. To install the latest development vesion of FW/1, simply enter `box install fw1-dev`. Refer to the [CommandBox documentation](https://ortus.gitbooks.io/commandbox-documentation/content/setup/installation.html) for more info on installing and using CommandBox.
 
-_This is a minimal install and only the `framework` folder is installed via this method_. To start with a complete working application, you can grab the `examples` folder from the full Github/RIAForge download (see the first install method) or generate one via [FW/1 Commands](https://github.com/framework-one/fw1-commands) from CommandBox.
+_This is a minimal install and only the `framework` folder is installed via this method_. To start with a complete working application, you can grab the `examples` folder from the full Github download (see the first install method) or generate one via [FW/1 Commands](https://github.com/framework-one/fw1-commands) from CommandBox.
 
 _**Note: do not install FW/1 into a subfolder that contains . in the name as this may prevent CFC resolution from working!**_
 

Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ I've been asked this several times recently so I figured it was worth a blog pos`
`9`	`9`
`10`	`10`	Okay, so why haven't I blogged about this before? Truth be told, I thought it was "obvious" how to find specific legacy releases on any Github project. Apparently, it is not obvious for everyone so it is worth blogging about. Every properly managed project on Github tags every official release so that all past releases can be found on the 'tags' page. You can see [FW/1's 'tags' page](https://github.com/framework-one/fw1/tags) where you can find every release since 1.0. Unfortunately, my choice of naming for tags has not always been consistent and I forgot the 'v' prefix for a while around the release of 2.0. Oops. Unfortunately the typical naming convention for prereleases tends to sort them above their gold release versions - see [Clojure's core.logic library's tags](https://github.com/clojure/core.logic/tags) for a more striking example. At least Github provides an easy mechanism for provided tagged archive releases.
`11`	`11`
`12`		-It's probably worth pointing out that downloading FW/1 directly from the [FW/1 RIAForge project page](http://fw1.riaforge.org/) will give you the latest stable release which is currently 2.1.1. That's because it downloads a ZIP file of the "master" branch from the Github site. All development is performed on the "develop" branch. The only time the RIAForge site will slip you something different is when a new release is in the Release Candidate stage and I update the RIAForge page to download a ZIP file of the "develop" branch - and I update the page to clearly state that! - and this is to increase adoption of the new release and help flush out any remaining bugs that haven't been caught during the alpha and beta testing phases.
	`12`	`+It's probably worth pointing out that downloading FW/1 directly from the [FW/1 GitHub project page](https://github.com/framework-one/fw1) will give you the latest stable release which is currently 2.1.1. That's because it downloads a ZIP file of the "master" branch from the Github site. All development is performed on the "develop" branch.`