Question: any plans to migrating from javax to jakarta package namespaces?

[al3xandru]

In Jakarta EE 9.1 APIs package namespace was changed from javax to jakarta. Jakarta EE 9.1 is supported by many popular frameworks like Quarkus, Helidon, etc.

Here are some links talking about this namespace change:

• Quarkus https://github.com/quarkusio/quarkus/issues/21574
• Helidon https://helidon.io/docs/v3/#/mp/guides/migration_3x

Are there any plans for such a migration in the k8s client?

[brendandburns]

I think it would be fine to migrate the javax.annotation.* to jakarta.annotation.* The other javax references are for SSL and I don't believe that is present in the jakarta namespace (nor do I necessarily want to switch ssl implementations)

But we'd definitely take a PR to update all of the annotations if you wanted to send it.

[Mohdcode]

/assign

[akshatarora0013]

/assign

[tmrpavan]

/assign

[tmrpavan]

@brendanburns, @yue9944882 Can you review my PR -> https://github.com/kubernetes-client/java/pull/2627

[brendandburns]

Some reference/background reading:

https://www.infoworld.com/article/3600158/enterprise-java-gets-a-new-namespace.html

[ann-ibm]

When the PR can be merged, with the spring security issue, we have to all go to Jakarta with Spring6, but it's also blocked with K8s-client and doesn't support Jarkarta.

Or can we have two build one with Jakarta, the other with javax?

[quietsnail]

@brendandburns When does kubernetes-client team plan to release jar file with Jakarta ?

[dasarathirout]

/assign

[aishuarya]

/assign

[abhinavvrm2020]

/assign