Handle empty top-level chapters about acorns

[msuchane]

Lenka, Gabi, and Lucie all prefer option 1 (empty files).

Alternatively, Lucie is partial to option 4 (commented-out includes) with an all-caps warning.

[jamsmithredhat]

James is ok with option 1 (empty files) or option 4 (commented-out includes).
Would like to see a solution soon.
Getting an error message, manually commenting out the include statement, and rebuilding is disruptive.
Even worse it the risk of commenting out an include statement and neglecting to uncomment it when you get some bugs that belong in the included file.
Thanks

[msuchane]

I'm happy with the "empty files" solution.

I was hesitant to implement it because empty assemblies technically violate FCC modularity rules, and our future tooling could have had a problem with it. At this point, it's no longer an issue, and I believe that the convenience of reliably working include statements greatly outweighs the theoretical modularity issues.

I'm going to implement this behavior shortly.

[msuchane]

@jamsmithredhat, I've resolved this issue, choosing option 1.

With version 1.0.0, acorns now generates empty AsciiDoc files for all top-level assemblies that are empty. As such, you can include all assemblies in your master file, and the include directives won't break.