Closed abelsromero closed 10 months ago
@aalmiray When you did the release, did you use JDK8?
I could reproduce that the module is set to the JDK used, at least with publishToMavenLocal
. But I am guessing, how is the release done btw?
Luckily, simply adding the toolchain to subprojects { ... }
fixes it for me.
java {
toolchain {
languageVersion = JavaLanguageVersion.of(8)
}
}
Btw, another thing, I initially got an error running publishToMavenLocal
, I had to delete this https://github.com/asciidoctor/asciidoctor-gradle-plugin/blob/d59ca0d667fb914cec12f402f8d9d00249b9b7e6/gradle/publishing.gradle#L117-L121
Invalid publication 'orgasciidoctorjvmepubPluginPluginMarkerMaven': POM file is invalid. Check any modifications you have made to the POM file.
with stacktrace
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Duplicated tag: 'description' (position: START_TAG seen ...</description>\n <description>... @10:16)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.checkFieldWithDuplicate(MavenXpp3Reader.java:140)
Can you PR that toolchain change, please?
The description change removes the description, I need to look into it more carefully. There's a dot being added at some point <description>.</description>
😮
The description change removes the description, I need to look into it more carefully. There's a dot being added at some point
<description>.</description>
😮
Yes, it is coming from somewhere else. I thought it best to get the update plugin suit out, rather than worry about fixing it at that point in time.
We should anyway rather refactor that pomXml code to be done in buildSrc
rather than in publishing.gradle
. It should also be easy to make it conditional to only be done when the maven-publish
plugin is applied in the build.
Thanks for the quick merge.
Yes, it is coming from somewhere else. I thought it best to get the update plugin suit out, rather than worry about fixing it at that point in time.
Not a problem 👍 But then, should we get 4.0.1 asap out and create a separated issue to discuss the "description" ?
create a separated issue to discuss the "description"
Yes.
@aalmiray When you did the release, did you use JDK8?
No, I used JDK11 as that's my default these days. Sorry, I'll use JDK8 for the patch release.
I am unable to bump form 3.3.2 to 4.0.0
More data:
asciidoctor-gradle-jvm-4.0.0.module
from local/caches
actually mentions java"org.gradle.jvm.version": 11,
. Code seems fine: CI; sourceCompatibility... is using Java8, but maybe the module picked up the version used during the release?