Update asset-pipeline GitHub URL

Author: jamesfredley

gradle/functional-test-config.gradle

@@ -54,7 +54,7 @@ configurations.configureEach {
     }
 }
 
-// work around for parallel builds due to https://github.com/bertramdev/asset-pipeline/issues/177
+// work around for parallel builds due to https://github.com/wondrify/asset-pipeline/issues/177
 if ('assetCompile' in tasks.names) {
     tasks.named('assetCompile').configure { Task task ->
         task.outputs.dir rootProject.layout.buildDirectory.dir('asset-serialize')

grails-doc/src/en/guide/commandLine/gradleBuild/gradlePlugins.adoc

@@ -47,9 +47,9 @@ The default plugins are as follows:
 * `com.github.erdi.webdriver-binaries` - A plugin that downloads and caches WebDriver binaries specific to the OS the build runs on. Read More: https://github.com/erdi/webdriver-binaries-gradle-plugin/blob/master/README.md[GitHub README]
 * `war` - The https://docs.gradle.org/{gradleVersion}/userguide/war_plugin.html[WAR plugin] changes the packaging so that Gradle creates a WAR file. You can comment out this plugin to build a runnable JAR file for standalone deployment.
 * `idea` - The IDEA plugin generates files used by http://www.jetbrains.com/idea/[IntelliJ IDEA], allowing the project to be opened from IDEA. Read More: https://docs.gradle.org/{gradleVersion}/userguide/idea_plugin.html[The IDEA Plugin]
-* `com.bertramlabs.asset-pipeline` - The https://github.com/bertramdev/asset-pipeline[Asset Pipeline] plugin enables compilation of static assets (JavaScript, CSS, etc.)
 * `application` - The Application plugin facilitates creating an executable JVM application. Read More: https://docs.gradle.org/{gradleVersion}/userguide/application_plugin.html[The Application Plugin]
 * `eclipse` - The Eclipse plugins generate files for the http://eclipse.org/[Eclipse IDE], enabling project import (File - Import... - Existing Projects into Workspace). Read More: https://docs.gradle.org/{gradleVersion}/userguide/eclipse_plugin.html[The Eclipse Plugin]
+* `asset-pipeline` - The https://github.com/wondrify/asset-pipeline[Asset Pipeline] plugin enables compilation of static assets (JavaScript, CSS, etc.)
 
 Many of these are built-in plugins provided by Gradle or third-party plugins. The Gradle plugins that Grails provides are as follows:
 

grails-doc/src/en/guide/commandLine/interactiveMode.adoc

@@ -178,7 +178,7 @@ Available Features
   mockito                             Mockito test mocking framework for JUnit
 
   View Rendering
-  asset-pipeline-grails (+)           The Asset-Pipeline is a plugin used for managing and processing static assets in JVM applications primarily via Gradle (however not mandatory). Read more at https://github.com/bertramdev/asset-pipeline
+  asset-pipeline-grails (+)           The Asset-Pipeline is a plugin used for managing and processing static assets in JVM applications primarily via Gradle (however not mandatory). Read more at https://github.com/wondrify/asset-pipeline
   grails-gsp (+)                      grails-gsp
   views-json                          JSON views are written in Groovy, end with the file extension gson and reside in the grails-app/views directory. They provide a DSL for producing output in the JSON format.
   views-markup                        Markup views are written in Groovy, end with the file extension gml and reside in the grails-app/views directory. They provide a DSL for producing output in the XML.

grails-doc/src/en/guide/theWebLayer/gsp/resources.adoc

@@ -17,7 +17,7 @@ specific language governing permissions and limitations
 under the License.
 ////
 
-Since version 3, Grails integrates with the https://github.com/bertramdev/asset-pipeline[Asset Pipeline plugin] to provide sophisticated static asset management. This plugin is installed by default in new Grails applications.
+Since version 3, Grails integrates with the https://github.com/wondrify/asset-pipeline[Asset Pipeline plugin] to provide sophisticated static asset management. This plugin is installed by default in new Grails applications.
 
 The basic way to include a link to a static asset in your application is to use the xref:../../../ref/Tags%20-%20GSP/resource.adoc[resource] tag. This simple approach creates a URI pointing to the file.