We should migrate our toolchain to use Rake instead of Bash or CMD scripts (currently we're using both, which is messy), since Rake is much more powerful, reduces build times (only updates files when their dependencies have changed), its simpler to sue (just rake anywhere in the repository) and works cross platform (no specific terminal required).
[x] Create Rake tasks for current tasks handled via scripts:
[x] Test suite.
[x] AsciiDoc Documentation:
[x] StdLib Manual
[x] Tutorials
[x] When all tasks can be handled using only Rake:
[x] Delete Bash and Batch build scripts.
[x] Cross Platform Rakefile — Initially Rake might require running in Bash due to the need of tools like SED, unix2dos, dos2unix, etc., but eventually all these operations need to be substituted using Ruby code so that Rake doesn't depend on Bash under Windows:
[x] Scripts sanitation without SED.
[x] EOL normalization without unix2dos/dos2unix.
[x] Other Bash tools or functionality in our scripts?
We've already adopted Rake in the ALAN i18n repository, with impressive results, and even created some custom Ruby/Rake modules for handling ALAN and Asciidoctor operation via custom methods/tasks which make handling entire folders just a matter of passing the folder path to the helper method — Rake will scan the folder contents and build the required tasks programmatically.
As mentioned in the tasks-list, some aspects of the toolchain rely on Unix tools which are only granted to be available on Bash under Windows, so we'll probably have to use Rake from Bash initially, until we manage to substitute the operations carried out by those Unix tools via Ruby code, so that our Rakefile can be run on any OS and terminal.
We should migrate our toolchain to use Rake instead of Bash or CMD scripts (currently we're using both, which is messy), since Rake is much more powerful, reduces build times (only updates files when their dependencies have changed), its simpler to sue (just
rakeanywhere in the repository) and works cross platform (no specific terminal required).We've already adopted Rake in the ALAN i18n repository, with impressive results, and even created some custom Ruby/Rake modules for handling ALAN and Asciidoctor operation via custom methods/tasks which make handling entire folders just a matter of passing the folder path to the helper method — Rake will scan the folder contents and build the required tasks programmatically.
As mentioned in the tasks-list, some aspects of the toolchain rely on Unix tools which are only granted to be available on Bash under Windows, so we'll probably have to use Rake from Bash initially, until we manage to substitute the operations carried out by those Unix tools via Ruby code, so that our Rakefile can be run on any OS and terminal.