Merge branch 'main' of github.com:propensive/scintillate

readme.md

@@ -22,9 +22,17 @@ container, preferably on a Loom-based JVM.
 - safe parameter and header access
 - typesafe representation of URLs
 
-## Availability
+## Availability Plan
 
-Scintillate has not yet been published as a binary.
+Scintillate has not yet been published. The medium-term plan is to build Scintillate
+with [Fury](/propensive/fury) and to publish it as a source build on
+[Vent](/propensive/vent). This will enable ordinary users to write and build
+software which depends on Scintillate.
+
+Subsequently, Scintillate will also be made available as a binary in the Maven
+Central repository. This will enable users of other build tools to use it.
+
+For the overeager, curious and impatient, see [building](#building).
 
 ## Getting Started
 
@@ -150,6 +158,7 @@ other representations can be used provided a `ToLocation` for that type is in co
 
 
 
+
 ## Status
 
 Scintillate is classified as __fledgling__. For reference, Scala One projects are
@@ -161,26 +170,62 @@ categorized into one of the following five stability levels:
 - _dependable_: production-ready, subject to controlled ongoing maintenance and enhancement; tagged as version `1.0.0` or later
 - _adamantine_: proven, reliable and production-ready, with no further breaking changes ever anticipated
 
-Projects at any stability level, even _embryonic_ projects, are still ready to
-be used, but caution should be taken if there is a mismatch between the
-project's stability level and the importance of your own project.
+Projects at any stability level, even _embryonic_ projects, can still be used,
+as long as caution is taken to avoid a mismatch between the project's stability
+level and the required stability and maintainability of your own project.
 
 Scintillate is designed to be _small_. Its entire source code currently consists
 of 376 lines of code.
 
 ## Building
 
-Scintillate can be built on Linux or Mac OS with [Fury](/propensive/fury), however
-the approach to building is currently in a state of flux, and is likely to
-change.
+Scintillate will ultimately be built by Fury, when it is published. In the
+meantime, two possibilities are offered, however they are acknowledged to be
+fragile, inadequately tested, and unsuitable for anything more than
+experimentation. They are provided only for the necessity of providing _some_
+answer to the question, "how can I try Scintillate?".
+
+1. *Copy the sources into your own project*
+
+   Read the `fury` file in the repository root to understand Scintillate's build
+   structure, dependencies and source location; the file format should be short
+   and quite intuitive. Copy the sources into a source directory in your own
+   project, then repeat (recursively) for each of the dependencies.
+
+   The sources are compiled against the latest nightly release of Scala 3.
+   There should be no problem to compile the project together with all of its
+   dependencies in a single compilation.
+
+2. *Build with [Wrath](https://github.com/propensive/wrath/)*
+
+   Wrath is a bootstrapping script for building Scintillate and other projects in
+   the absence of a fully-featured build tool. It is designed to read the `fury`
+   file in the project directory, and produce a collection of JAR files which can
+   be added to a classpath, by compiling the project and all of its dependencies,
+   including the Scala compiler itself.
+
+   Download the latest version of
+   [`wrath`](https://github.com/propensive/wrath/releases/latest), make it
+   executable, and add it to your path, for example by copying it to
+   `/usr/local/bin/`.
+
+   Clone this repository inside an empty directory, so that the build can
+   safely make clones of repositories it depends on as _peers_ of `scintillate`.
+   Run `wrath -F` in the repository root. This will download and compile the
+   latest version of Scala, as well as all of Scintillate's dependencies.
+
+   If the build was successful, the compiled JAR files can be found in the
+   `.wrath/dist` directory.
 
 ## Contributing
 
-Contributors to Scintillate are welcome and encouraged. New contributors may like to look for issues marked
-<a href="https://github.com/propensive/scintillate/labels/beginner">beginner</a>.
+Contributors to Scintillate are welcome and encouraged. New contributors may like
+to look for issues marked
+[beginner](https://github.com/propensive/scintillate/labels/beginner).
 
-We suggest that all contributors read the [Contributing Guide](/contributing.md) to make the process of
-contributing to Scintillate easier.
+We suggest that all contributors read the [Contributing
+Guide](/contributing.md) to make the process of contributing to Scintillate
+easier.
 
 Please __do not__ contact project maintainers privately with questions unless
 there is a good reason to keep them private. While it can be tempting to
@@ -189,29 +234,33 @@ audience, and it can result in duplication of effort.
 
 ## Author
 
-Scintillate was designed and developed by Jon Pretty, and commercial support and training is available from
-[Propensive O&Uuml;](https://propensive.com/).
+Scintillate was designed and developed by Jon Pretty, and commercial support and
+training on all aspects of Scala 3 is available from [Propensive
+O&Uuml;](https://propensive.com/).
 
 
 
 ## Name
 
 To _scintillate_ is "to fluoresce momentarily when struck by a charged particle", much as a web server is dormant until an incoming request stimulates a response.
 
-In general, Scala One project names are always chosen with some rationale, however it is usually
-frivolous. Each name is chosen for more for its _uniqueness_ and _intrigue_ than its concision or
-catchiness, and there is no bias towards names with positive or "nice" meanings—since many of the
-libraries perform some quite unpleasant tasks.
+In general, Scala One project names are always chosen with some rationale,
+however it is usually frivolous. Each name is chosen for more for its
+_uniqueness_ and _intrigue_ than its concision or catchiness, and there is no
+bias towards names with positive or "nice" meanings—since many of the libraries
+perform some quite unpleasant tasks.
 
-Names should be English words, though many are obscure or archaic, and it should be noted how
-willingly English adopts foreign words. Names are generally of Greek or Latin origin, and have
-often arrived in English via a romance language.
+Names should be English words, though many are obscure or archaic, and it
+should be noted how willingly English adopts foreign words. Names are generally
+of Greek or Latin origin, and have often arrived in English via a romance
+language.
 
 ## Logo
 
 The logo shows four interlocked three-pointed stars, intended to look like flying sparks or scintillations.
 
 ## License
 
-Scintillate is copyright &copy; 2023 Jon Pretty & Propensive O&Uuml;, and is made available under the
-[Apache 2.0 License](/license.md).
+Scintillate is copyright &copy; 2024 Jon Pretty & Propensive O&Uuml;, and
+is made available under the [Apache 2.0 License](/license.md).
+

src/server/server.scala

@@ -1,5 +1,5 @@
 /*
-    Scintillate, version [unreleased]. Copyright 2023 Jon Pretty, Propensive OÜ.
+    Scintillate, version [unreleased]. Copyright 2024 Jon Pretty, Propensive OÜ.
 
     The primary distribution site is: https://propensive.com/
 

src/servlet/servlet.scala

@@ -1,5 +1,5 @@
 /*
-    Scintillate, version [unreleased]. Copyright 2023 Jon Pretty, Propensive OÜ.
+    Scintillate, version [unreleased]. Copyright 2024 Jon Pretty, Propensive OÜ.
 
     The primary distribution site is: https://propensive.com/
 

src/test/tests.scala

@@ -1,5 +1,5 @@
 /*
-    Scintillate, version [unreleased]. Copyright 2023 Jon Pretty, Propensive OÜ.
+    Scintillate, version [unreleased]. Copyright 2024 Jon Pretty, Propensive OÜ.
 
     The primary distribution site is: https://propensive.com/