Permalink
Browse files

Change our URL to bazel.build

--
MOS_MIGRATED_REVID=137500893
  • Loading branch information...
1 parent 9facc29 commit 4885eefffe11d5623eb478328f9fdc88fbcc6345 @damienmg damienmg committed with katre Oct 28, 2016
View
@@ -19,7 +19,7 @@ possibly guide you.
### Code reviews and other contributions.
**All submissions, including submissions by project members, require review.**
-Please follow the instructions in [the contributors documentation](http://bazel.io/contributing.html).
+Please follow the instructions in [the contributors documentation](http://bazel.build/contributing.html).
### The small print
Contributions made by corporations are covered by a different agreement than
View
@@ -1,4 +1,4 @@
-# [Bazel](http://bazel.io) ([Beta](http://bazel.io/roadmap.html#beta))
+# [Bazel](http://bazel.build) ([Beta](http://bazel.build/roadmap.html#beta))
*{Fast, Correct} - Choose two*
@@ -21,21 +21,21 @@ support many different programming languages within Google, and can be
used to build both client and server software targeting multiple
architectures from the same underlying codebase.
-Find more background about Bazel in our [FAQ](http://bazel.io/faq.html).
+Find more background about Bazel in our [FAQ](http://bazel.build/faq.html).
## Getting Started
- * How to [install Bazel](http://bazel.io/docs/install.html)
- * How to [get started using Bazel](http://bazel.io/docs/getting-started.html)
- * The Bazel command line is documented in the [user manual](http://bazel.io/docs/bazel-user-manual.html)
- * The rule reference documentation is in the [build encyclopedia](http://bazel.io/docs/be/overview.html)
- * How to [use the query command](http://bazel.io/docs/query.html)
- * How to [extend Bazel](http://bazel.io/docs/skylark/index.html)
- * The test environment is described on the page [writing tests](http://bazel.io/docs/test-encyclopedia.html)
+ * How to [install Bazel](http://bazel.build/docs/install.html)
+ * How to [get started using Bazel](http://bazel.build/docs/getting-started.html)
+ * The Bazel command line is documented in the [user manual](http://bazel.build/docs/bazel-user-manual.html)
+ * The rule reference documentation is in the [build encyclopedia](http://bazel.build/docs/be/overview.html)
+ * How to [use the query command](http://bazel.build/docs/query.html)
+ * How to [extend Bazel](http://bazel.build/docs/skylark/index.html)
+ * The test environment is described on the page [writing tests](http://bazel.build/docs/test-encyclopedia.html)
## About the Bazel project:
- * How to [contribute to Bazel](http://bazel.io/contributing.html)
- * Our [governance plan](http://bazel.io/governance.html)
- * Future plans are in the [roadmap](http://bazel.io/roadmap.html)
- * For each feature, which level of [support](http://bazel.io/support.html) to expect.
+ * How to [contribute to Bazel](http://bazel.build/contributing.html)
+ * Our [governance plan](http://bazel.build/governance.html)
+ * Future plans are in the [roadmap](http://bazel.build/roadmap.html)
+ * For each feature, which level of [support](http://bazel.build/support.html) to expect.
View
@@ -154,7 +154,7 @@ function bazel_build() {
cp -f bazel-genfiles/scripts/packages/bazel.dsc $1/bazel.dsc
cp -f bazel-genfiles/scripts/packages/bazel.tar.gz $1/bazel.tar.gz
fi
- cp bazel-genfiles/site/jekyll-tree.tar $1/www.bazel.io.tar
+ cp bazel-genfiles/site/jekyll-tree.tar $1/www.bazel.build.tar
cp bazel-genfiles/scripts/packages/README.md $1/README.md
fi
@@ -224,7 +224,7 @@ Classpath exception. Those installers should always be redistributed along with
the source code.
_Security_: All our binaries are signed with our
-[public key](https://bazel.io/bazel-release.pub.gpg).
+[public key](https://bazel.build/bazel-release.pub.gpg).
"
if [ ! -x "${release_tool}" ]; then
@@ -254,7 +254,7 @@ function create_index_md() {
echo
# Security notice
echo "_Security_: All our binaries are signed with our"
- echo "[public key](https://bazel.io/bazel-release.pub.gpg)."
+ echo "[public key](https://bazel.build/bazel-release.pub.gpg)."
echo
for f in $1/*.sha256; do # just list the sha256 ones
local filename=$(basename $f .sha256);
@@ -165,7 +165,7 @@ pkg_deb(
"bash-completion",
],
description_file = "debian/description",
- homepage = "http://bazel.io",
+ homepage = "http://bazel.build",
maintainer = "The Bazel Authors <bazel-dev@googlegroups.com>",
package = "bazel",
version_file = ":version.txt",
@@ -38,14 +38,14 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
<title>bazel (Install)</title>
<authors>The Bazel Authors</authors>
<!-- projectUrl is required for the community feed -->
- <projectUrl>https://bazel.io</projectUrl>
+ <projectUrl>https://bazel.build</projectUrl>
<iconUrl>https://cdn.rawgit.com/bazelbuild/bazel/master/site/images/bazel-logo.png</iconUrl>
<copyright>Copyright 2016 The Bazel Authors. All rights reserved.</copyright>
<!-- If there is a license Url available, it is is required for the community feed -->
<licenseUrl>https://github.com/bazelbuild/bazel/tree/master/LICENSE.txt</licenseUrl>
<requireLicenseAcceptance>true</requireLicenseAcceptance>
<projectSourceUrl>https://github.com/bazelbuild/bazel.git</projectSourceUrl>
- <docsUrl>https://www.bazel.io/versions/master/docs/getting-started.html</docsUrl>
+ <docsUrl>https://www.bazel.build/versions/master/docs/getting-started.html</docsUrl>
<mailingListUrl>https://groups.google.com/forum/#!forum/bazel-discuss</mailingListUrl>
<bugTrackerUrl>https://github.com/bazelbuild/bazel/issues</bugTrackerUrl>
<tags>bazel build automation</tags>
@@ -68,5 +68,5 @@ You also need, in your msys2 environment:
export BAZEL_SH=c:/tools/msys64/usr/bin/bash.exe
export BAZEL_PYTHON=c:/tools/python2/python.exe
-See also https://bazel.io/docs/windows.html
+See also https://bazel.build/docs/windows.html
"@
@@ -16,4 +16,4 @@ Description: Bazel is a tool that automates software builds and tests.
executable programs and libraries, and assembling deployable packages
for Android, iOS and other target environments. Bazel is similar to
other tools like Make, Ant, Gradle, Buck, Pants and Maven.
-Homepage: http://bazel.io
+Homepage: http://bazel.build
@@ -100,7 +100,7 @@ test_write() {
if ! which unzip >/dev/null; then
echo >&2
echo "unzip not found, please install the corresponding package." >&2
- echo "See http://bazel.io/docs/install.html for more information on" >&2
+ echo "See http://bazel.build/docs/install.html for more information on" >&2
echo "dependencies of Bazel." >&2
exit 1
fi
@@ -125,7 +125,7 @@ fi
if [ ! -x "${JAVA_HOME}/bin/javac" ]; then
echo >&2
echo "Java not found, please install the corresponding package" >&2
- echo "See http://bazel.io/docs/install.html for more information on" >&2
+ echo "See http://bazel.build/docs/install.html for more information on" >&2
echo "dependencies of Bazel." >&2
exit 1
fi
@@ -183,6 +183,6 @@ Make sure you have "${bin}" in your path. You can also activate bash
completion by adding the following line to your ${BASHRC}:
source ${base}/bin/bazel-complete.bash
-See http://bazel.io/docs/getting-started.html to start a new project!
+See http://bazel.build/docs/getting-started.html to start a new project!
EOF
exit 0
@@ -52,7 +52,7 @@ function build_and_serve {
pkill -9 jekyll || true
if [ -z "$TARGET" ]; then
- echo "Serving bazel.io site at port $PORT"
+ echo "Serving bazel.build site at port $PORT"
jekyll serve --detach --quiet --port $PORT --source $WORKING_DIR
else
TMP_TARGET=$(mktemp -d)
@@ -6,13 +6,13 @@
<script>
var current_url = window.location.href;
- var bad_url = new RegExp("^https?://bazelbuild.github.io/bazel/");
+ var bad_url = new RegExp("^https?://(bazelbuild.github.io/bazel|bazel.io)/");
if (bad_url.test(current_url)) {
- window.location.replace(current_url.replace(bad_url, "https://www.bazel.io/"));
+ window.location.replace(current_url.replace(bad_url, "https://bazel.build/"));
}
- var http_url = new RegExp("^http://(www\.)?bazel.io/");
+ var http_url = new RegExp("^http://(www\.)?bazel.build/");
if (http_url.test(current_url)) {
- window.location.replace(current_url.replace(http_url, "https://www.bazel.io/"));
+ window.location.replace(current_url.replace(http_url, "https://bazel.build/"));
}
</script>
@@ -88,7 +88,7 @@
</li>
<li><a href="{{ page.version_prefix }}/docs/skylark/cookbook.html">Examples</a></li>
<li><a href="{{ page.version_prefix }}/docs/skylark/deploying.html">Packaging rules</a></li>
- <li><a href="https://skydoc.bazel.io" target="_blank">Documenting rules</a></li>
+ <li><a href="https://skydoc.bazel.build" target="_blank">Documenting rules</a></li>
</ul>
</nav>
</div>
View
@@ -5,7 +5,7 @@
<channel>
<title>Bazel Blog</title>
- <link>http://bazel.io</link>
+ <link>http://bazel.build</link>
<description>Fast, correct builds.</description>
{% for post in site.categories.blog limit:10 %}
<item>
@@ -98,7 +98,7 @@ def _impl(ctx):
that every provider is associated with its declaration (it is a different
type). Arguments of a provider declaration when used as a function are
exactly the same as that of a built-in `struct` function.
-* [Target](http://www.bazel.io/docs/skylark/lib/Target.html) objects become
+* [Target](http://www.bazel.build/docs/skylark/lib/Target.html) objects become
dictionaries of providers indexed by their declaration. Bracket notation can
be used to retrieve a particular provider. Thus, provider declarations are
[symbol-like](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Symbol)
@@ -137,7 +137,7 @@ find easily what can go in the deps attribute of cc_library).
We allow rules to declare the providers they intend to return with a `providers`
argument of a
-<code>[rule](http://www.bazel.io/docs/skylark/lib/globals.html#rule)</code>
+<code>[rule](http://www.bazel.build/docs/skylark/lib/globals.html#rule)</code>
function. It is an error if the rule implementation function does not return all
the providers listed in `providers`. It may however return additional providers.
@@ -32,7 +32,7 @@ directory: to remove all external artifacts, use `bazel clean --expunge`.
By default, external dependencies are fetched as needed during `bazel build`. If
you would like to disable this behavior or prefetch dependencies, use
-[`bazel fetch`](http://bazel.io/docs/bazel-user-manual.html#fetch).
+[`bazel fetch`](http://bazel.build/docs/bazel-user-manual.html#fetch).
## Using Proxies
@@ -127,8 +127,8 @@ There are a few basic types of external dependencies that can be created.
If you have a second Bazel project that you'd like to use targets from, you can
use
-[`local_repository`](http://bazel.io/docs/be/workspace.html#local_repository)
-or [`http_archive`](http://bazel.io/docs/be/workspace.html#http_archive)
+[`local_repository`](http://bazel.build/docs/be/workspace.html#local_repository)
+or [`http_archive`](http://bazel.build/docs/be/workspace.html#http_archive)
to symlink it from the local filesystem or download it (respectively).
For example, suppose you are working on a project, `my-project/`, and you want
@@ -150,8 +150,8 @@ If your coworker has a target `//foo:bar`, your project can refer to it as
## Depending on non-Bazel projects
Rules prefixed with `new_` (e.g.,
-[`new_local_repository`](http://bazel.io/docs/be/workspace.html#new_local_repository)
-and [`new_http_archive`](http://bazel.io/docs/be/workspace.html#new_http_archive)
+[`new_local_repository`](http://bazel.build/docs/be/workspace.html#new_local_repository)
+and [`new_http_archive`](http://bazel.build/docs/be/workspace.html#new_http_archive)
) allow you to create targets from projects that do not use Bazel.
For example, suppose you are working on a project, `my-project/`, and you want
@@ -54,7 +54,7 @@ Note: You might need to `sudo apt-get install software-properties-common` if you
```
$ echo "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list
-$ curl https://bazel.io/bazel-release.pub.gpg | sudo apt-key add -
+$ curl https://bazel.build/bazel-release.pub.gpg | sudo apt-key add -
```
If you want to use the JDK 7, please replace `jdk1.8` with `jdk1.7` and if you want to install the testing version of Bazel, replace `stable` with `testing`.
@@ -231,7 +231,7 @@ This will create a bazel binary in `bazel-bin/src/bazel`. This binary is
self-contained, so it can be copied to a directory on the PATH (e.g.,
`/usr/local/bin`) or used in-place.
-Check our [continuous integration](http://ci.bazel.io) for the current status of
+Check our [continuous integration](http://ci.bazel.build) for the current status of
the build.
@@ -119,7 +119,7 @@ itself and its dependencies.
Above, we argued that in order to be correct, Bazel needs to know all the input
files that go into a build step in order to detect whether that build step is
still up-to-date. The same is true for package loading and rule analysis, and we
-have designed [Skyframe] (http://www.bazel.io/docs/skyframe.html) to handle this
+have designed [Skyframe] (http://www.bazel.build/docs/skyframe.html) to handle this
in general. Skyframe is a graph library and evaluation framework that takes a
goal node (such as ‘build //foo with these options’), and breaks it down into
its constituent parts, which are then evaluated and combined to yield this
@@ -115,7 +115,7 @@ Bazel binary in /usr/bin.
If your repository is under the [bazelbuild organization](https://github.com/bazelbuild),
contact the [bazel-dev](https://groups.google.com/forum/#!forum/bazel-dev) list
-to have it added to [ci.bazel.io](http://ci.bazel.io).
+to have it added to [ci.bazel.build](http://ci.bazel.build).
## Documentation
@@ -63,7 +63,7 @@ release candidate, we release it.
### Release versioning
Version 0.1 is our first release marking the start of our beta phase. Until version 1.0.0, we
-increase the MINOR version every time we reach a [new milestone](http://bazel.io/roadmap.html).
+increase the MINOR version every time we reach a [new milestone](http://bazel.build/roadmap.html).
Version 1.0.0 marks the end of our beta phase; afterwards, we will label each release with a
version number of the form MAJOR.MINOR.PATCH according to the
@@ -256,7 +256,7 @@ $ ls $WORKSPACE/bazel-bin/android
You can now deploy the app to a connected Android device or emulator from the
command line using the
-[`bazel mobile-install`](http://bazel.io/docs/bazel-user-manual.html#mobile-install)
+[`bazel mobile-install`](http://bazel.build/docs/bazel-user-manual.html#mobile-install)
command. This command uses the Android Debug Bridge (`adb`) to communicate with
the device. You must set up your device to use `adb` following the instructions
in
@@ -270,7 +270,7 @@ $ bazel mobile-install //android:android
```
Note that the `mobile-install` subcommand also supports the
-[`--incremental`](http://bazel.io/docs/bazel-user-manual.html#mobile-install)
+[`--incremental`](http://bazel.build/docs/bazel-user-manual.html#mobile-install)
flag that can be used to deploy only those parts of the app that have changed
since the last deployment.
@@ -51,7 +51,7 @@ The key files and directories are:
## Update the WORKSPACE file
As with the Android app, you must add references to
-[external dependencies](http://bazel.io/docs/external.html) to your `WORKSPACE`
+[external dependencies](http://bazel.build/docs/external.html) to your `WORKSPACE`
file. For the backend server, these are references to the App Engine SDK,
the Java Servlet SDK and other libraries needed to build the App Engine
applications.
@@ -20,7 +20,7 @@
/**
* Utility class that encapsulates dependencies from sharding implementations
- * on the test environment. See http://bazel.io/docs/test-sharding.html for a
+ * on the test environment. See http://bazel.build/docs/test-sharding.html for a
* list of all environment variables related to test sharding.
*/
public class ShardingEnvironment {
@@ -87,10 +87,10 @@ public Metadata getMetadata() {
<p>Note that the maven_jar name is used as a repository name, so it is limited by the rules
governing workspace names: it cannot contain dashes nor dots (see
-<a href="http://bazel.io/docs/be/functions.html#workspace">the documentation on workspace names</a>
-for the exact specification). By convention, maven_jar names should match the artifact name,
-replacing illegal characters with underscores and leaving off the version. For example, a rule
-with <code>artifact = "org.apache.commons:commons-lang3:3.4"</code> should have
+<a href="http://bazel.build/docs/be/functions.html#workspace">the documentation on workspace
+names</a> for the exact specification). By convention, maven_jar names should match the artifact
+name, replacing illegal characters with underscores and leaving off the version. For example, a
+rule with <code>artifact = "org.apache.commons:commons-lang3:3.4"</code> should have
<code>name = "org_apache_commons_commons_lang3"</code>.</p>
<h4 id="maven_jar_examples">Examples</h4>
@@ -31,7 +31,7 @@
public static final String SANDBOX_NOT_SUPPORTED_MESSAGE =
"Sandboxed execution is not supported on your system and thus hermeticity of actions cannot "
- + "be guaranteed. See http://bazel.io/docs/bazel-user-manual.html#sandboxing for more "
+ + "be guaranteed. See http://bazel.build/docs/bazel-user-manual.html#sandboxing for more "
+ "information. You can turn off this warning via --ignore_unsupported_sandboxing";
@SuppressWarnings("unchecked")
@@ -53,7 +53,7 @@
/**
* General documentation block of the method. See the skylark documentation at
- * http://www.bazel.io/docs/skylark/.
+ * http://www.bazel.build/docs/skylark/.
*/
String doc() default "";
@@ -85,4 +85,4 @@ Finally, update the rules:
* * *
### Updating anything else in the directory
-Follow usual procedure as described on https://www.bazel.io/contributing.html
+Follow usual procedure as described on https://www.bazel.build/contributing.html
@@ -140,7 +140,7 @@ reproducible.
## Pulling images and deb files from the internet
If you do not want to check in base image in your repository, you can use
-[external repositories](http://bazel.io/docs/external.html). For instance,
+[external repositories](http://bazel.build/docs/external.html). For instance,
you could create various layer with `external` labels:
```python
@@ -58,7 +58,7 @@ pkg_deb(
"unzip",
],
description_file = "debian/description",
- homepage = "http://bazel.io",
+ homepage = "http://bazel.build",
maintainer = "The Bazel Authors <bazel-dev@googlegroups.com>",
package = "bazel",
version = "0.1.1",

0 comments on commit 4885eef

Please sign in to comment.