Róbert Papp
Róbert Papp
Unblocks https://github.com/gradle-nexus/publish-plugin/pull/299
I'm yet to do a full review, thanks for looking @3flex !
The default artifact will still be published even when an artifact ID has been explicitly specified.
Beautiful report! Based on what you have in OP, I think this is WAI because we have 3 publications in the logs: ``` > Task :publishMavenJavaPublicationToMavenLocal > Task :publishOsgiPluginPluginMarkerMavenPublicationToMavenLocal >...
The default artifact will still be published even when an artifact ID has been explicitly specified.
even in `afterEvaluate`?
The default artifact will still be published even when an artifact ID has been explicitly specified.
That's so weird, looking.
The default artifact will still be published even when an artifact ID has been explicitly specified.
Ah, the error is not that it's not found, but it by default includes the Java component, see `org.gradle.plugin.devel.plugins.MavenPluginPublishPlugin`. Here's what I would go with: use all the built-ins and...
The default artifact will still be published even when an artifact ID has been explicitly specified.
I'm not sure what we could add, @szpak thoughts? Note: this plugin is a generic publishing plugin, publishing Gradle plugins still uses all the same facilities, except Gradle provided plugin...
Closing this, it'll require a manual update. This should show up on dependency dashboard as "ignored".
```kotlin package app.cash.paparazzi.sample import org.junit.Test class UnsatisfiedLinkErrorTest { @Test fun test() { println(android.animation.ValueAnimator()) } } ```
Yes, but I think the test is not meant to be a Paparazzi test. This implies that if a module has Paparazzi, it cannot have any other complex tests.