asciidoctorj
asciidoctorj copied to clipboard
asciidoctor
Expose the logging to Gradle
Not sure if I describe this issue correctly but during an Asciidoctor presentation at Javaland I asked if the Gradle plug-in could cancel the build if an include could not be found.
If I understood @aalmiray correct, this would require that asciidoctorj exposed the log via its API so that the Gradle plug-in can use this to decide if it wants to cancel the build.
This request has a hard dependency on https://github.com/asciidoctor/asciidoctor/issues/44. At the moment, AsciidoctorJ doesn't have access to the log messages. I know this is an important one.
The reason it's this way is because these log messages were put in place long before we ever dreamed of AsciidoctorJ existing. It's time to refactor.
I told Lars to open an issue so that we don't lose track of it :)
I was unaware of the issue in Asciidoctor core but it's good to have this issue as well as both projects will require changes.
Am Dienstag, 8. März 2016 schrieb Dan Allen :
The reason it's this way is because these log messages were put in place long before we ever dreamed of AsciidoctorJ existing. It's time to refactor.
— Reply to this email directly or view it on GitHub https://github.com/asciidoctor/asciidoctorj/issues/440#issuecomment-193996947 .
Please, it's a year since the last message. Is there any update on accessing log messages from within asciidoctorJ?
I can say with some level of confidence :soon:. I'm going to try to tackle this for 1.5.7. The solution has to come in core, so it's really waiting on me. But even I need this feature badly, so we're in the same boat.