Merge pull request #34 from ausimian/fix/appup-compiler-naming

docs: name only the relup task for Castle

Author: ausimian

README.md

@@ -11,9 +11,13 @@ upgrades. This includes:
     the standard Mix launcher.
 
 Additionally, `Forecastle` ships with an appup compiler and a mix task for relup
-generation. Both are named for `Castle` rather than for the package that
-implements them - `mix castle.relup` and the `:appup` compiler - because where the
-build-time code lives is a packaging decision, and what a developer types is not.
+generation. The task is `mix castle.relup`, named for `Castle` rather than for
+the package that implements it, because where the build-time code lives is a
+packaging decision and what a developer types is not.
+
+The compiler is named for neither package. It is `mix compile.appup`, reached
+through the project's `:compilers` list rather than invoked by name, so there is
+no `mix castle.appup`.
 
 ## Installation
 

lib/mix/tasks/castle.relup.ex

@@ -2,8 +2,8 @@ defmodule Mix.Tasks.Castle.Relup do
   @moduledoc """
   Generate a relup file between releases.
 
-  This task is provided by `Forecastle`, Castle's build-time half, and named
-  `castle.*` like the rest of the tooling a developer runs.
+  This task is provided by `Forecastle`, Castle's build-time half, and named for
+  `Castle` because that is the package a project depends on.
 
   `mix castle.relup` will generate a relup between a `target` release and
   any number of other releases. The paths specifed in the options should