https://github.com/jenkinsci/aws-java-sdk-plugin/ is a multi-module project publishing parts of the AWS Java SDK as separate plugins.
Historically, this was a single fat plugin with all jars from the AWS Java SDK. Over the years, it grew a lot, and I split <https://groups.google.com/g/jenkinsci-dev/c/RPWxsPKBaZ8/m/U3_Upc7kAQAJ> the project in finer-grain modules to avoid everyone from requiring the fat plugin. Eventually all plugins in the Jenkins ecosystem can either: 1. Depend on the fat plugin 2. Depend on one or many of the fine-grained library plugins (recommended) 3. Depend directly on AWS Java SDK jars, bundling them in their plugin. Ideally there should not be any more plugin using 1., at the time I split the fat plugin, I also filed corresponding pull requests to update plugins to use 2. instead. 3. is not recommended because it adds weight in general to update centers, JENKINS_HOME, as well as making things more complicated to handle in case a security fix is required in the AWS Java SDK. Instead, it is recommended to add the corresponding modules as fine-grained plugins to the existing project, using the documented <https://github.com/jenkinsci/aws-java-sdk-plugin/#adding-a-new-plugin> procedure. Therefore, I propose to remove the fat aws-java-sdk plugin. This will reduce the required storage for each new release, as well as prompt any remaining plugin that may depend on the fat plugin to do the right thing, and implement option 2. Any concern with this proposal? Please let me know. Cheers, Vincent -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCiZ1P0AvOVM1bgZhMxc6FLyHioUWzney5jcfXjAm8rVjg%40mail.gmail.com.
