I've fixed, or created PRs for the rest of them -
https://github.com/jenkins-infra/plugins-wiki-docs/pull/2
On Monday, December 20, 2021 at 3:18:34 PM UTC-8 Gavin Mogan wrote:
> In my little audit of the plugin site, I got reports about an HTTP
> image in the docs (would produce mixed content
In my little audit of the plugin site, I got reports about an HTTP
image in the docs (would produce mixed content warning).
https://plugins.jenkins.io/monkit-plugin/
http://www.novonordisk.dk/Images/apis.png
Not only does that image not exist, but praqma.net and code.praqma.net
don't exist, so
On Mon, Dec 20, 2021 at 1:53 PM 'Jesse Glick' via Jenkins Developers
wrote:
>
> Is this mostly about Servlet API types, or other EE packages?
Servlet types and JavaMail were the most common cases I saw in the
prototype, along with a new package namespace for FileUpload to go
along with the new
On Sun, Dec 19, 2021 at 9:13 PM Basil Crow wrote:
> When loading plugins without "Jakarta-Ready: true" in a Jakarta EE 9
> environment, we will probably need to apply some special compatibility
> transformations, exempli gratia, transforming the binaries after
> exploding the plugin or loading
On Fri, Dec 17, 2021 at 5:34 PM Basil Crow wrote:
> I suppose by the same logic we should remove
> access-modifier-annotation, spotbugs-annotations, and
> animal-sniffer-annotations from plugin-pom as well.
>
To the extent that you can verify that these libraries would be in the
classpath for
Hi Oleg,
The knowledge transfer was mentioned in my original email, I didn't see
volunteers for org admins. Nonetheless, let me follow up w/ a doodle for
timing, for after the new years, and we'll take it from there.
Thank you,
alyssa
On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev
wrote:
>
