publishMultiversionMicrosite and fix GHPagesPlugin publishing #388
Conversation
calvellido
changed the title
| @@ -450,6 +449,9 @@ trait MicrositeAutoImportSettings extends MicrositeKeys { | |||
| makeMultiversionMicrosite := { | |||
| Def.sequential(createMicrositeVersions, clean, makeVersionedMicrosite, moveMicrositeVersions) | |||
| }.value, | |||
| ghpagesPrivateMappings := { | |||
| sbt.Path.allSubpaths((target in makeSite).value).toList | |||
There was a problem hiding this comment.
I guess this is what makes the trick for both publishMicrosite and publishMultiversionMicrosite, correct?
There was a problem hiding this comment.
Yes it is!
publishMicrosite and publishMultiversionMicrosite are just different compositions of other tasks, with both of them including pushSite. This task will be the one affected by this ghpagesPrivateMappings, where in the case of using GHPagesPlugin, instead of recreate the site, the content to be uploaded will be read from target in makeSite (i.e. project/target/site).
Probably in the future we might want to simplify the command, and just use one approach or the other depending on the settings established by the user (e.g. micrositeVersionList values).
I ended up defining the task directly, instead of using an auxiliary one, which in the end it was only adding boilerplate IMO.
pushMicrositeGHPagesPlugin case.publishMultiversionMicrositetask to publish exactly that :)