From b8a85f935b18c1e2507e7214b87a655ecf16b480 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Wed, 19 Oct 2011 10:56:18 -0400 Subject: [PATCH] change a few links to go to newer rather than older pages. --- Index.md | 19 +++++++++++++------ Inspecting-Settings.md | 2 +- Quick-Configuration-Examples.md | 7 ++++--- Tasks.md | 4 +++- 4 files changed, 21 insertions(+), 11 deletions(-) diff --git a/Index.md b/Index.md index 459df33..93e0ebc 100644 --- a/Index.md +++ b/Index.md @@ -44,7 +44,9 @@ For available plugins, see [[sbt 0.10 plugins list]]. * [Artifact] represents a single artifact (such as a jar or a pom) to be built and published. See [[Library Management]] and [[Artifacts]]. * A [Resolver] can resolve and retrieve dependencies. Many types of Resolvers can publish dependencies as well. A repository is a closely linked idea that typically refers to the actual location of the dependencies. However, sbt is not very consistent with this terminology and repository and resolver are occasionally used interchangeably. * A [ModuleConfiguration] defines a specific resolver to use for a group of dependencies. -* A [Configuration] is a useful Ivy construct for grouping dependencies. See [[Configurations]]. It is also used for scoping [[Settings]]. +* A [Configuration] is a useful Ivy construct for grouping + dependencies. See [[Configurations]]. It is also used for + [[scoping settings|Getting Started Scopes]]. * `Compile`, `Test`, `Runtime`, `Provided`, and `Optional` are predefined [[Configurations]]. ### Settings and Tasks @@ -74,12 +76,17 @@ For available plugins, see [[sbt 0.10 plugins list]]. ### Settings and Tasks -See [[Settings]] and [[Tasks]] for details. +See the [[Getting Started Guide|Getting Started Basic Def]] for details. -* `:=`, `<<=`, `+=`, `++=`, `~=`, `<+=`, `<++=` These construct a [Setting], which is the fundamental type in the [[Settings]] system. -* `map` This defines a task initialization that uses other tasks or settings. See [[Tasks]]. It is a common name used for many other types in Scala, such as collections. -* `apply` This defines a setting initialization using other settings. It is not typically written out. See [[Settings]]. This is a common name in Scala. -* `in` specifies the [Scope] or part of the [Scope] of a setting being referenced. See [[Settings]]. +* `:=`, `<<=`, `+=`, `++=`, `~=`, `<+=`, `<++=` These construct a + [Setting], which is the fundamental type in the + [[settings|Getting Started Basic Def]] system. +* `map` This defines a task initialization that uses other tasks + or settings. See + [[more about settings|Getting Started More About Settings]]. It is a common name used for many other types in Scala, such as collections. +* `apply` This defines a setting initialization using other settings. It is not typically written out. See [[more about settings|Getting Started More About Settings]]. This is a common name in Scala. +* `in` specifies the [Scope] or part of the [Scope] of a setting + being referenced. See [[scopes|Getting Started Scopes]]. ### File and IO diff --git a/Inspecting-Settings.md b/Inspecting-Settings.md index 8e7fc92..df467f5 100644 --- a/Inspecting-Settings.md +++ b/Inspecting-Settings.md @@ -2,7 +2,7 @@ Central to sbt is the new configuration system, which is designed to enable extensive customization. The goal of this page is to explain the general model behind the configuration system and how to work with it. -[[Basic Configuration]] describes how to define settings; this page describes interacting with them and exploring them at the command line. +The Getting Started Guide (see [[.sbt files|Getting Started Basic Def]]) describes how to define settings; this page describes interacting with them and exploring them at the command line. # Selecting commands, tasks, and settings diff --git a/Quick-Configuration-Examples.md b/Quick-Configuration-Examples.md index 3eb2fb9..c55d2a0 100644 --- a/Quick-Configuration-Examples.md +++ b/Quick-Configuration-Examples.md @@ -1,8 +1,9 @@ [sbt.SettingDefinition]: http://harrah.github.com/xsbt/latest/api/sbt/Init$SettingsDefinition.html -Listed here are some examples of settings (each setting is independent). See [[Basic Configuration]] for details. +Listed here are some examples of settings (each setting is +independent). See [[.sbt build definition|Getting Started Basic Def]] for details. -_Please note_ that blank lines are used to separate individual settings. Avoid using blank lines within a single multiline expression. As explained in [[Settings]], each setting is otherwise a normal Scala expression with expected type [sbt.SettingDefinition]. +_Please note_ that blank lines are used to separate individual settings. Avoid using blank lines within a single multiline expression. As explained in [[.sbt build definition|Getting Started Basic Def]], each setting is otherwise a normal Scala expression with expected type [sbt.SettingDefinition]. ```scala // set the name of the project @@ -180,4 +181,4 @@ credentials += Credentials(Path.userHome / ".ivy2" / ".credentials") // Directly specify credentials for publishing. credentials += Credentials("Sonatype Nexus Repository Manager", "nexus.scala-tools.org", "admin", "admin123") -``` \ No newline at end of file +``` diff --git a/Tasks.md b/Tasks.md index 4b8122b..d0bae8b 100644 --- a/Tasks.md +++ b/Tasks.md @@ -35,7 +35,9 @@ There are several features of the task system: 6. Each task has access to its own Logger that by default persists the logging for that task at a more verbose level than is initially printed to the screen. These features are discussed in detail in the following sections. -The context for the code snippets will be either the body of a `Build` object in a [[Full Configuration]] or an expression in a `build.sbt` [[Basic Configuration]]. +The context for the code snippets will be either the body of a +`Build` object in a [[.scala file|Getting Started Full Def]] or an +expression in a [[build.sbt|Getting Started Basic Def]]. # Defining a New Task