anchor.diff:  
   [source,shell]
   ----
  -$ quarkus build
  +quarkus build
   [INFO] Scanning for projects...
   [INFO]
   [INFO] ---------------------< org.acme:code-with-quarkus >---------------------
  
positive.code: 
  [source,shell]
  ----
  $ quarkus ext list --concise -i -s jdbc
  JDBC Driver - DB2                                  quarkus-jdbc-db2
  JDBC Driver - PostgreSQL                           quarkus-jdbc-postgresql
  JDBC Driver - H2                                   quarkus-jdbc-h2
  
negative.code: - Given the `2.0.0.Final` version of the CLI, specifying `-P :quarkus-universe-bom:` is equivalent to `-P io.quarkus:quarkus-universe-bom:2.0.0.Final`.
  - Specifying `-P 999-SNAPSHOT` is equivalent to `-P io.quarkus:quarkus-bom:999-SNAPSHOT`
  +
  Note: default values are subject to change. Using the `--dry-run` option will show you the computed value.
  
  2. Specify a Platform Stream
  +
  Platform streams are new in Quarkus 2.0. 
  +
  A platform stream operates against a remote registry. Each registry defines one or more platform streams, and each stream defines one or more platform release BOM files that define how projects using that stream should be configured.
  +
  Streams are identified using `platformKey:streamId` syntax. A specific stream can be specified using `-S platformKey:streamId`. When specifying a stream, empty segments will be replaced with _discovered_ defaults, based on stream resource resolution rules.
  +
  For `2.0.0.Final`, you must enable the registry client (`--registry-client`) explicitly to specify a stream. This is not required for `2.1.0.Final` or later releases.
  
  == Dealing with extensions
  
  [source,shell]
  ----
  quarkus ext --help
  ----
  
  === Listing extensions
  