Zongle Wang
Zongle Wang
Duplicate of #246
From my observation, Spotless and this plugin itself don't have plugin marker artifacts, but Detekt does. Note that they both use GNPP for Maven Central publishing. Are you saying that...
Publishing my project to MavenLocal and view the plugin marker artifact: ```xml 13:08:30: Executing 'publishToMavenLocal --no-configuration-cache'... > Task :compileJava FROM-CACHE > Task :compileGroovy NO-SOURCE > Task :pluginDescriptors > Task :processResources...
Initially, I requested that GNPP's own marker artifacts to be published. I was trying to repro if GNPP correctly supports publishing marker artifacts, seems not. Probably we should file a...
The default artifact will still be published even when an artifact ID has been explicitly specified.
Seems can't: ``` Publication with name 'pluginMaven' not found. ``` `publishing.publications` is empty.
The default artifact will still be published even when an artifact ID has been explicitly specified.
```kt publishing { publications { afterEvaluate { named("pluginMaven") { ... } } } } ``` ``` FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring...
The default artifact will still be published even when an artifact ID has been explicitly specified.
Thanks a lot! It works for me now. Should we note this in README or fallback it?
@gabrielittner Could you check the box to trigger the renovate config migration for json5?
There is no plaintext parser or `RichTextState.toPlainText` API, can we consider providing a new access for this?
Thanks! That would be very handy. As a workaround, I'm converting plaintext from the output markdown.