Fix issue running AsciidoctorJ out of process on Gradle 4.10 #269

ysb33r · 2018-11-03T13:32:17Z

Running something like

asciidoctorPdf {
    inProcess OUT_OF_PROCESS
    logDocuments true
    sourceDir 'src/docs/asciidoc'

    sources {
        include 'subdir/sample2.ad'
    }
}

will fail with an error

Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. Module [groovy-all is loaded in version 2.4.12 and you are trying to load version 2.4.15
	at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$DefaultModuleListener.onModule(MetaClassRegistryImpl.java:513)
	at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromProperties(ExtensionModuleScanner.java:80)
	at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromMetaInf(ExtensionModuleScanner.java:74)
	at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanClasspathModules(ExtensionModuleScanner.java:56)
	at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:113)
	at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:74)
	at groovy.lang.GroovySystem.<clinit>(GroovySystem.java:36)

The text was updated successfully, but these errors were encountered:

GEM support: - Add compatibility test for gems support plugin. Reveal.js: - Reveal.js plugin & base plugin. - `revealjs` extension. - `revealjsPlugins` extension. - Plugin support is ignored if reveal.js backend < 1.2.0. - Compatibility test checks for content in generated files. JDK & Gradle support: - Upgradle build to 4.8.1. - Test with JDK8, JDK10, JDK11 on Travis. - Add Gradle 4.10.2 & Gradle 5.10-rc-1 to compatibility matrix. - Minimum Gradle version for compatibility testing on JDK11 is 4.8.1. - Use at least Jacoco 0.8.3 for JDK11. - Inject Guava classpath for Gradle 4.8. - Make publishing Gradle 5.0 compatible. - Work around Gradle 5.0 worker classpath leakage Miscellaneous: - Add upgrading note regarding extensions. - GitHub archives unpack in a repository-branch pattern. - Compatibility Asciidoctor Task will support legacy attributes. In order to ease migration `legacyAttributes=true` can be set on the compatibility conversion task. This will enable `projectdir` and `rootdir` attributes. it will also print a warning message to change the usage to the new attributes. - Under test if the Groovy versions are different, then run using JAVA_EXEC instead (asciidoctor#269).

ragnor · 2019-01-18T13:22:11Z

Hi,
Is there any way to run version 1.5.9.2 on gradle 5.1.1 so below exception won't occur:

Exception in thread "main" java.lang.ExceptionInInitializerError
        at org.codehaus.groovy.runtime.InvokerHelper.<clinit>(InvokerHelper.java:86)
        at groovy.lang.GroovyObjectSupport.getDefaultMetaClass(GroovyObjectSupport.java:59)
        at groovy.lang.GroovyObjectSupport.<init>(GroovyObjectSupport.java:32)
        at groovy.lang.Reference.<init>(Reference.java:38)
        at org.asciidoctor.gradle.backported.AsciidoctorJavaExec.main(AsciidoctorJavaExec.groovy:188)
Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. Module [groovy-all is loaded in version 2.5.4 and you are trying to load version 2.4.12
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$DefaultModuleListener.onModule(MetaClassRegistryImpl.java:523)
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromProperties(ExtensionModuleScanner.java:87)
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromMetaInf(ExtensionModuleScanner.java:81)
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanClasspathModulesFrom(ExtensionModuleScanner.java:63)
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanClasspathModules(ExtensionModuleScanner.java:55)
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:124)
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:85)
        at groovy.lang.GroovySystem.<clinit>(GroovySystem.java:36)
        ... 5 more

ysb33r · 2019-01-18T14:36:49Z

Try using 2.0-alpha.5 instead.

We are only plannign to do a small maintenance releases on 1.5.x and currently there is no plan to fully support it on Gradle 5.x once the 2.x version of the plugin is released.

ragnor · 2019-01-18T14:51:29Z

Thank you for the answer.
Unfortunately I'm using Spring REST Docs that requires asciidoctor 1.5.x. What is surprising downgrading to 1.5.3 (this one is suggested in Spring REST Docs documentation) seams to solve the issue.
With 2.0-alpha.5 and gradle 5.1.1 I had an issue Exception in thread "main" java.lang.ClassNotFoundException: com.google.common.collect.ImmutableSet$SerializedForm

shevek · 2019-02-10T23:12:20Z

Asciidoctor 1.5.9.2 doesn't work on 4.10.3 either, even in-process.
Version 1.5.3 does. Also downgrading as workaround.

AD 1.5.9.2 DID work on Gradle 4.5.1, so something changed.

wimdeblauwe · 2019-02-20T17:21:33Z

Also had to downgrade to 1.5.3 to work with Gradle 5.2.1

ysb33r · 2019-02-20T20:07:11Z

@wimdeblauwe @shevek @ragnor Are any of you using build.gradle.kts instead of build.gradle ?

wimdeblauwe · 2019-02-21T07:13:15Z

@wimdeblauwe @shevek @ragnor Are any of you using build.gradle.kts instead of build.gradle ?

Not me

shevek · 2019-02-24T01:06:41Z

We are using build.gradle in groovy, no kts here.

shevek · 2019-02-25T00:20:11Z

The issue is that AbstractAsciidoctorTask is including everything plus the kitchen sink on the classpath when it invokes an external JVM. Heaven only knows why half that stuff is on there, there's at least 3 groovy versions that I can see. It's including the entire runtime classpath for the project without even doing dependency resolution. So yes, it's SNAFU'd.

ysb33r · 2019-03-02T23:04:48Z

I think I have tracked down the issue. I might do a maintenance release within the next two weeks. Time is limited atm.

asciidoctor#269)

…res (asciidoctor#269)

…iidoctor#269)

ysb33r · 2019-04-23T08:16:07Z

Finally got to do the fix for this after 2.1.0 was released and 2.2.0 work has bene prepped.

The fix will be released in 1.5.12 and 1.6.1. Will get @aalmiray to release when he has the time.

shevek · 2019-05-28T01:36:25Z

Is there a release of 1.5.12? asciidoctor just broke for us globally with no change on our side, so we're hunting for a bunch of outstanding fixes. :(

ysb33r · 2019-05-28T08:19:25Z

Yes 1.5.12 & 1.6.1 was released some weeks ago.

shevek · 2019-05-28T23:15:12Z

Thank you. Didn't see it on Central. See it now in Gradle plugins.

ysb33r · 2019-05-29T08:11:24Z

Closing thisissue. Please raise a new one if you still see something similar.

ysb33r added bug 2.x Issue related to the 2.x series labels Nov 3, 2018

ysb33r added this to the 2.0.0 milestone Nov 3, 2018

ysb33r self-assigned this Nov 3, 2018

ysb33r mentioned this issue Nov 3, 2018

Tracking 2.0.0 Development #240

Closed

28 tasks

ysb33r added the 1.[56].x Issues related to the 1.5.x/1.6.x series label Mar 3, 2019

ysb33r modified the milestones: 2.0.0, 1.5.9.3 / 1.5.10 Mar 22, 2019

ysb33r added a commit to ysb33r/asciidoctor-gradle-plugin that referenced this issue Apr 23, 2019

Remove automatic placement of Gradle's groovy-all Jar on the classpath (

eb8dc01

asciidoctor#269)

ysb33r added a commit to ysb33r/asciidoctor-gradle-plugin that referenced this issue Apr 23, 2019

Only add ScriptOrigin to classpath if extensions are written as closu…

a64915e

…res (asciidoctor#269)

ysb33r added a commit to ysb33r/asciidoctor-gradle-plugin that referenced this issue Apr 23, 2019

Only add local groovy to classpath if no other Groovy Jar exists (asc…

88aae70

…iidoctor#269)

ysb33r added a commit to ysb33r/asciidoctor-gradle-plugin that referenced this issue Apr 23, 2019

Only add local groovy to classpath if no other Groovy Jar exists (asc…

13838e4

…iidoctor#269)

ysb33r modified the milestones: 1.5.9.3 / 1.5.10, 1.5.12 Apr 23, 2019

ysb33r added a commit that referenced this issue Apr 23, 2019

Only add local groovy to classpath if no other Groovy Jar exists (#269)

33d1ab4

ysb33r closed this as completed May 29, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix issue running AsciidoctorJ out of process on Gradle 4.10 #269

Fix issue running AsciidoctorJ out of process on Gradle 4.10 #269

ysb33r commented Nov 3, 2018

ragnor commented Jan 18, 2019 •

edited

Loading

ysb33r commented Jan 18, 2019 •

edited

Loading

ragnor commented Jan 18, 2019

shevek commented Feb 10, 2019 •

edited

Loading

wimdeblauwe commented Feb 20, 2019

ysb33r commented Feb 20, 2019

wimdeblauwe commented Feb 21, 2019

shevek commented Feb 24, 2019

shevek commented Feb 25, 2019

ysb33r commented Mar 2, 2019

ysb33r commented Apr 23, 2019

shevek commented May 28, 2019

ysb33r commented May 28, 2019

shevek commented May 28, 2019

ysb33r commented May 29, 2019

Fix issue running AsciidoctorJ out of process on Gradle 4.10 #269

Fix issue running AsciidoctorJ out of process on Gradle 4.10 #269

Comments

ysb33r commented Nov 3, 2018

ragnor commented Jan 18, 2019 • edited Loading

ysb33r commented Jan 18, 2019 • edited Loading

ragnor commented Jan 18, 2019

shevek commented Feb 10, 2019 • edited Loading

wimdeblauwe commented Feb 20, 2019

ysb33r commented Feb 20, 2019

wimdeblauwe commented Feb 21, 2019

shevek commented Feb 24, 2019

shevek commented Feb 25, 2019

ysb33r commented Mar 2, 2019

ysb33r commented Apr 23, 2019

shevek commented May 28, 2019

ysb33r commented May 28, 2019

shevek commented May 28, 2019

ysb33r commented May 29, 2019

ragnor commented Jan 18, 2019 •

edited

Loading

ysb33r commented Jan 18, 2019 •

edited

Loading

shevek commented Feb 10, 2019 •

edited

Loading