Documentation

[sormuras]

Blog Posts

Show the usage of Bach and its features.

1. Introduction
2. Zero-Installation & Zero-Configuration
3. The Build Module bach.info and the Project Descriptor @ProjectInfo
4. Details of the Build Module .bach/bach.info/module-info.java

Javadoc

Technical details.

• JDK with foundation tools
• Bach uses JDK's ToolProvider API and provides IO-releated functions
• Declared, System, and External Modules
• Project model with declarative project-info support
• Extending Bach

Snippets

• https://github.com/sormuras/bach/tree/master/doc
• Bach 11.x https://sormuras.github.io/blog/2020-05-11-bach-intro-1.html
• Bach 11.x https://sormuras.github.io/blog/2020-09-03-bach-simplicissimus.html

[sormuras]

Yeah, I left the path of "zero-installation" and "zero-configuration" in favor of a small and well-defined installation of Bach local to the project. The "zero-xyz" magic are still possible to implement, but even small projects tend to need at least a few custom configurations. One thing, I wasn't willing to give up, was the 100% Java path. Hence, Bach will support xml, yml, ... files, not even for tiny configurations. The canonical way to setup a modular Java project with Bach 17-ea, is to create a ".bach/" directory and store everything Bach-related there. This includes a copy of the com.github.sormuras.bach module, stored in .bach/bin/com.github.sormuras.bach@VERSION.jar. Right next to some supporting scripts, like a platform-agnostic JShell overlay or platform-dependent launchers. Those launchers take care of setting up the compilation environment in order to build your project according to the configurations declared the bach.info module.
Take a look at this project as an example: https://github.com/sormuras/modules -- Bach's usage is shown in a GitHub {workflow](https://github.com/sormuras/modules/blob/ab6a80c58107d4ff8c46c627d421cecca4db7a6d/.github/workflows/release.yml#L23-L24).