> On 28. Aug 2018, at 15:10, Oleg Nenashev <[email protected]> wrote:
>
> I can imagine a local company which installs a single localization plugin
> That's why I lean towards having separate plugins for each locale.
… and an aggregator. It's free. Only needs updates whenever a locale plugin is
added or removed. I really don't understand the resistance here.
> Depends on the installation logic implementation, but generally "yes".
Which installation logic would you consider to be supported (i.e. we wouldn't
close a related Jira issue immediately) and does not install whatever is
available on your chosen update site? CLI command, UI, even install-plugins.sh
and configuration-as-code plugin install the newest available release of
dependencies.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/0E887029-C05B-430F-8371-B61838D08682%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
