Migration to Java11 and modules

I’m currently starting the Java 11 migration of my plugins and my local builds are failing due to several Java modules failures (package x.y.z is declared in the unnamed module, but a.b.c does not use it, error: module not found: x.y.z). Do we already have some guidelines on how to migrate a

Re: Migration to Java11 and modules

I'm not aware of hitting any modules issues, this is the normal pull request that has been applied: https://github.com/jenkinsci/support-core-plugin/pull/421 at a guess 30+ plugins with no issues, likely more. On Tue, 3 Jan 2023 at 13:08, Ullrich Hafner wrote: > I’m currently starting the Java

Re: Migration to Java11 and modules

On Tue, Jan 3, 2023 at 8:08 AM Ullrich Hafner wrote: > Do we already have some guidelines on how to migrate a plugin to Java 11? Yes; normally there is very little to do. > Do we need to create module-info.java files for plugins? No. > How do we access libraries that use modules? >

Re: User.CanonicalIdResolver extension point "context"

On Fri, Dec 30, 2022 at 8:17 AM Cristian Morales Vega wrote: > I am looking at https://issues.jenkins.io/browse/JENKINS-70342, but > I'm not sure how the "context" in CanonicalIdResolver is supposed to > be used. The only thing I have seen in the docs is "Can be used (for > example) to

Re: Migration to Java11 and modules

> Am 03.01.2023 um 15:42 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Tue, Jan 3, 2023 at 8:08 AM Ullrich Hafner > wrote: >> Do we already have some guidelines on how to migrate a plugin to Java 11? > > Yes; normally there is very little to do. >