I'd love to see more info about this. I had similar difficulty
understanding the difference back when I was working on the secret
textarea UI widget, and I had wanted to do some research to write a
blog post about it, but that was well over a year ago by now.
On Mon, Jul 27, 2020 at 11:06 AM Jesse
On Fri, Jul 24, 2020 at 10:52 AM mike cirioli wrote:
> Thanks for the description Jesse
Sure; want to write up a jenkins.io patch?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails f
Thanks for the description Jesse, thats probably the clearest I have seen it
explained so far :)
-mike
——
“What makes us unhappy is to want. Yet if we would learn to cut our wants to
nothing, the smallest thing we’d get would be a true gift.”
― Carlos Castaneda, Separate Reality: Conversation
Thanks for the explanation.
The documentation I was referring to is:
https://wiki.jenkins.io/display/JENKINS/Defining+a+new+extension+point
On Friday, July 24, 2020 at 5:50:15 PM UTC+5:30 Jesse Glick wrote:
> An `ExtensionPoint` is implemented by classes marked `@Extension`,
> which are singlet
An `ExtensionPoint` is implemented by classes marked `@Extension`,
which are singletons contributed by plugins, sometimes known as a
service registry pattern. This is the fundamental mechanism by which
Jenkins plugins add functionality. An admin does not configure the
_set_ of extensions, though a
Hi all,
In the documentation, it says that for an extension point where "users
should be able to configure zero or more instances of some things you
define", Describable/Descriptor pattern is preferred over Singleton
pattern.
>From a design point of view, which pattern is better when impleme
