Closed abelsromero closed 7 months ago
I don't know what caused the maven-shade-plugin
to be added in the first place but I did some end-2-end tests (java 17) and without it, the project build fine, IT run, and can be consumed without having to embed dependencies (these are resolved and installed by Maven).
The shade-plugin alters the pom.xml removing runtime dependencies. This makes that components consuming asciidoclet cannot resolve required dependencies like AsciidoctorJ, causing conversion to fail.
closes #120