mirror of https://github.com/sbt/sbt.git
commit
f2e75c0811
|
|
@ -48,7 +48,7 @@ The field-specific API (contributed in addition to the parts common to all defin
|
|||
* The API of associated setters and getters.
|
||||
|
||||
=== Type Parameters ===
|
||||
Type parameters are not a definition, but they are used by methods, classes, and type members. The important aspects of a type parameter are its position in its defining parameter list and its upper and lower bounds, which are types. The actual name of a type parameter is not imporant, but it needs to be uniquely referenced within a source file.
|
||||
Type parameters are not a definition, but they are used by methods, classes, and type members. The important aspects of a type parameter are its position in its defining parameter list and its upper and lower bounds, which are types. The actual name of a type parameter is not important, but it needs to be uniquely referenced within a source file.
|
||||
|
||||
The API contributed by a type parameter section is:
|
||||
* The API of each type parameter in the type parameter section, in order. The number of type parameters is implicit here.
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ The default configuration file for sbt looks like:
|
|||
project.initialize: quick=set(true), new=set(true)
|
||||
}}}
|
||||
|
||||
The `scala.version` property specifies the version of Scala used to run the application. If specified, the `scala.classifiers`property defines classifers such as 'sources' of extra Scala artifacts to retrieve. The `app.org`, `app.name`, and `app.version` properties specify the organization, module ID, and version of the application, respectively. These are used to resolve and retrieve the application from the repositories listed in `[repositories]`. If `app.cross-versioned` is true, the resolved module ID is `{app.name+'_'+scala.version}`. The paths given in `app.resources` are added to the application's classpath. If the path is relative, it is resolved against the application's working directory.
|
||||
The `scala.version` property specifies the version of Scala used to run the application. If specified, the `scala.classifiers`property defines classifiers such as 'sources' of extra Scala artifacts to retrieve. The `app.org`, `app.name`, and `app.version` properties specify the organization, module ID, and version of the application, respectively. These are used to resolve and retrieve the application from the repositories listed in `[repositories]`. If `app.cross-versioned` is true, the resolved module ID is `{app.name+'_'+scala.version}`. The paths given in `app.resources` are added to the application's classpath. If the path is relative, it is resolved against the application's working directory.
|
||||
|
||||
Jars are retrieved to the directory given by `boot.directory`. You can make this an absolute path to be shared by all sbt instances on the machine. You might see messages like:
|
||||
{{{
|
||||
|
|
@ -140,7 +140,7 @@ Once the final configuration is resolved, the launcher proceeds to obtain the ne
|
|||
{{{
|
||||
${boot.directory}/${scala.version}/lib/
|
||||
}}}
|
||||
If this directory already exists, the launcher takes a shortcut for startup performance and assumes that the jars have already been downloaded. If the directory does not exist, the launcher uses Apache Ivy to resolve and retrieve the jars. A similar process occurs for the application itself. It and its dependencies are retreived to
|
||||
If this directory already exists, the launcher takes a shortcut for startup performance and assumes that the jars have already been downloaded. If the directory does not exist, the launcher uses Apache Ivy to resolve and retrieve the jars. A similar process occurs for the application itself. It and its dependencies are retrieved to
|
||||
{{{
|
||||
${boot.directory}/${scala.version}/${app.org}/${app.name}/.
|
||||
}}}
|
||||
|
|
|
|||
Loading…
Reference in New Issue