-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version overridden when also referencing asciidoctor-pdf #239
Comments
You can also do classpath 'org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16', {
exclude module : 'asciidoctorj'
} |
@mrotteveel Have you managed to resolve this issue? |
@ysb33r The workaround works, but I consider the behavior itself a bug. |
This is resolved in the 2.0-alpha.3 release, where one can control the versions in a simplified way, but still with fine granularity. You will definitely no longer need any of the buildscript ugliness of 1.5.x. AAMOF you could just apply the org.asciidoctor.jvm.pdf plugin which will give you an asciidoctorPdf task. |
Ok, thanks! |
This is a temporary measure until clarity can be obtained from the JRuby team why this failure is occurring on 9.2.0.+.
This is a temporary measure until clarity can be obtained from the JRuby team why this failure is occurring on 9.2.0.+.
When only using the html5 backend with asciidoctor-gradle-plugin 1.5.7, asciidoctorj 1.5.6 is used (the generated html has
<meta name="generator" content="Asciidoctor 1.5.6.1">
).If I reference
org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16
because I also want to generate PDF, then this is overridden and 1.5.5 is used (<meta name="generator" content="Asciidoctor 1.5.5">
), even when explicitly specifying the version in the asciidoctorj tag. This probably happens becauseasciidoctorj-pdf:1.5.0-alpha.16
explicitly depends on asciidoctorj 1.5.5.I'd expect the version declared in the asciidoctorj task to take precedence.
build.gradle:
As a workaround, I need to explicitly add a dependency on
org.asciidoctor:asciidoctorj:1.5.6
(uncomment it in the build.gradle above).The text was updated successfully, but these errors were encountered: