This message was deleted.
# community-support
s
This message was deleted.
v
Maybe with
--info
, latest with
--debug
. Make sure you do not just publish the plugin code artifact, but also the marker artifacts which are necessary to resolve plugin id to code artifact.
j
I do the the marker artifacts in the repository
neither --info nor --debug log the http calls
Copy code
2023-12-14T16:06:52.471+0100 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Plugin [id: 'com.malt.phase-duration'] was not found in any of the following sources:
2023-12-14T16:06:52.471+0100 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-12-14T16:06:52.471+0100 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] - Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
2023-12-14T16:06:52.471+0100 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] - Plugin Repositories (plugin dependency must include a version number for this source)
in settings.gradle.kts, in pluginManagement plugins I declare
Copy code
id("com.malt.phase-duration-plugin") version "bf4112187f4ced395b9a3851b579cdec715f592c"
so I'm not sure why it complais about the version number maybe it actually fails before trying to actually resolve it
v
Because your IDs are different
-plugin
suffix
j
🤦
v
And using a Git SHA as version is not the best idea, as then version ordering is totally mixed up
j
thanks for your help
👌 1
I understand the risks with git SHA
👌 1
I'll search for a way to enforce strict versions for the plugin declarations or to find an alterantive versionning scheme that can still easily be automated we are trying to move away from buildSrc to released plugins for both regular and convention plugins, using included builds results in a massive performance degradation. ( dependency resolution gets triggers during config phase which is single threaded )
but we would like to avoid having to manually release and update the versions for our internal plugins which are tied to the mono repo
config cache doesn't help since some of our external plugins don't play nice with it 😕
v
Make them become nice. 🙂 Config cache is scheduled to become default-enabled in 2024. 🎉
j
yeah I wish
but some are way beyond my capabilities
not to mention the lack of time 😞
😭 1