aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/blog/_posts/2016-06-10-0.3.0-release.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/blog/_posts/2016-06-10-0.3.0-release.md')
-rw-r--r--site/blog/_posts/2016-06-10-0.3.0-release.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/site/blog/_posts/2016-06-10-0.3.0-release.md b/site/blog/_posts/2016-06-10-0.3.0-release.md
index 0da207e0e6..d8a97c3a71 100644
--- a/site/blog/_posts/2016-06-10-0.3.0-release.md
+++ b/site/blog/_posts/2016-06-10-0.3.0-release.md
@@ -9,18 +9,18 @@ Bazel. This milestone is marked by support for IDE integration but also major
features such as remote caching of build artifacts and experimental Windows
support.
-## Improvements from our [roadmap](http://bazel.io/roadmap.html)
+## Improvements from our [roadmap](http://bazel.build/roadmap.html)
### IDE support
In this release, we made it possible to [generate information for IDEs from
-Bazel build files](http://bazel.io/blog/2016/06/10/ide-support.html) using
-[Skylark aspects](http://bazel.io/docs/skylark/aspects.html).
+Bazel build files](http://bazel.build/blog/2016/06/10/ide-support.html) using
+[Skylark aspects](http://bazel.build/docs/skylark/aspects.html).
Simultaneous with Bazel 0.3 release, we are announcing the availability of two
projects integrating Bazel with different IDEs:
-* [Tulsi](http://tulsi.bazel.io) is an Xcode plugin for Bazel. This is the same
+* [Tulsi](http://tulsi.bazel.build) is an Xcode plugin for Bazel. This is the same
plugin that teams inside Google use for developing iOS applications.
* [e4b](https://github.com/bazelbuild/e4b) is an experimental Eclipse plugin for
Bazel. It was made to illustrate the use of Skylark aspects for IDE
@@ -29,7 +29,7 @@ projects integrating Bazel with different IDEs:
### Windows support
-Bazel can now bootstrap on [Windows](http://bazel.io/docs/windows.html) without
+Bazel can now bootstrap on [Windows](http://bazel.build/docs/windows.html) without
admin privilege and can use the Microsoft Visual C++ toolchain. Windows
support is still highly experimental and we have identified
[several issues](https://github.com/bazelbuild/bazel/issues?q=is%3Aissue+is%3Aopen+label%3A%22category%3A+multi-platform+%3E+windows%22)
@@ -46,16 +46,16 @@ with Alpha to enhance that support.
### Skylark remote repositories
Remote repository rules can now be created using
-[Skylark](http://bazel.io/docs/skylark/repository_rules.html). This can be used
+[Skylark](http://bazel.build/docs/skylark/repository_rules.html). This can be used
to support your custom protocols, interfacing with new packaging systems or even
do auto-configuration to use a toolchain on your local disk. We use it
-especially to have [a better out-of-the-box experience with C++ toolchains](http://www.bazel.io/blog/2016/03/31/autoconfiguration.html).
+especially to have [a better out-of-the-box experience with C++ toolchains](http://www.bazel.build/blog/2016/03/31/autoconfiguration.html).
## Other major changes since 0.2.0
* We just open-sourced our BUILD file formatter, [buildifier](https://github.com/bazelbuild/buildifier).
* We now provide a Debian APT repository for installing bazel, see the
- [installation guide](http://bazel.io/docs/install.html) on how to use it.
+ [installation guide](http://bazel.build/docs/install.html) on how to use it.
* Our JUnit test runner for Java tests (`--nolegacy_bazel_java_test`) is now the
default.
@@ -68,7 +68,7 @@ changes.
Looking ahead to 0.4.0:
* The last blockers for `--strategy=worker=Javac` will be resolved, making Java
- builds [faster](http://www.bazel.io/blog/2015/12/10/java-workers.html).
+ builds [faster](http://www.bazel.build/blog/2015/12/10/java-workers.html).
* [Yue](https://github.com/hermione521) has made great progress in making
[Ulf](https://github.com/ulfjack)'s prototype of [sandboxing for OS
X](https://github.com/bazelbuild/bazel/tree/osx-sandbox-hardlinks) real.