Merge pull request cds-hooks#585 from buildpacks/using-project-descriptor

Update all project descriptors to schema-version 0.2

Author: AidanDelaney

content/docs/app-developer-guide/specify-buildpacks.md

@@ -54,24 +54,25 @@ pack build sample-java-maven-app \
 
 ## Using a Project Descriptor
 
-The [`project.toml`][project-toml] format allows for Buildpack URIs to be specified in the `[[build.buildpacks]]` table with the `uri` key.
+The [`project.toml`][project-toml] format allows for Buildpack URIs to be specified in the `[[io.buildpacks.group]]` table with the `uri` key.
 
 ##### Example:
 
 ```toml
-[project]
+[_]
+schema-version = "0.3"
 id = "sample-java-maven-app"
 name = "Sample Java App"
 version = "1.0.0"
 
-[[build.buildpacks]]
+[[io.buildpacks.group]]
 uri = "samples/java-maven"
 
-[[build.buildpacks]]
+[[io.buildpacks.group]]
 uri = "samples/buildpacks/hello-processes/"
 
-[[build.buildpacks]]
-uri = "docker://cnbs/sample-package:hello-univers"
+[[io.buildpacks.group]]
+uri = "docker://cnbs/sample-package:hello-universe"
 ```
 
 ## URI Examples

content/docs/app-developer-guide/using-inline-buildpacks.md

@@ -6,22 +6,23 @@ summary="Learn how to create an ephemeral buildpack to customize your build."
 
 You can supplement your app's build process with custom scripts by creating an _inline buildpack_. An inline buildpack is an ephemeral buildpack that's defined in your [project descriptor][project-toml] (i.e. `project.toml`). You can include a script to run as part of the build without setting up all the files and directories that are required for a complete buildpack.
 
-Inline buildpacks are defined as an entry in the `[[build.buildpacks]]` table of the project descriptor by including an `inline` script in the `[build.buildpacks.script]` table.
+Inline buildpacks are defined as an entry in the `[[io.buildpacks.group]]` table of the project descriptor by including an `inline` script in the `[io.buildpacks.group.script]` table.
 
 For example, you may want to run a Rake task against a Ruby app after the Ruby buildpack builds your app.
 
 ```toml
-[project]
+[_]
+schema-version = "0.2"
 id = "io.buildpacks.my-app"
 
-[[build.buildpacks]]
+[[io.buildpacks.group]]
 id = "example/ruby"
 version = "1.0"
 
-[[build.buildpacks]]
+[[io.buildpacks.group]]
 id = "me/rake-tasks"
 
-  [build.buildpacks.script]
+  [io.buildpacks.group.script]
   api = "0.6"
   inline = "rake package"
 ```
@@ -33,10 +34,10 @@ In this example, the `me/rake-tasks` inline buildpack is configured to run after
 Inline buildpacks aren't constrained to a single command, however. You can define complex scripts as [heredocs](https://toml.io/en/v1.0.0#string) in your project descriptor. For example, this snippet of a descriptor will source a shell script contained in the app repo, use it to modify the app directory (and thus the files that go into the final image), and create slices for the app:
 
 ```toml
-[[build.buildpacks]]
+[[io.buildpacks.group]]
 id = "me/cleanup"
 
-  [build.buildpacks.script]
+  [io.buildpacks.script]
   api = "0.9"
   inline = """
 set -e

content/docs/reference/config/project-descriptor.md

@@ -95,6 +95,7 @@ The schema for the `project descriptor` is:
 An example `project.toml` is:
 ```toml
 [_]
+schema-version = "0.2"
 id = "io.buildpacks.my-app"
 version = "0.1"