Hi Konrad,
On 02.01.2025 11:54, Konrad Windszus wrote:
From a consumer perspective I am very much against same name class names in
different packages. Leads to lot of issues with IDEs (auto-import) and wrongly
imported packages (particularly with non-recommended star imports).
very good point, yes we should avoid duplicate class names (this is one
of the reasons why we prefixed some interfaces with "Sling" like
HttpServletRequest).
I am in favour of a (stable) Jakarta infix in the name like
SlingJakartaHttpServletRequest. I think those are sufficiently stable/accurate
for the foreseeable future. Having them in a dedicated package makes sense
though for the version range imports.
Agree, that using "Jakarta" should be stable, and if not we can create
new versions with the new name :)
I changed this now for all the relevant interfaces and classes but kept
them in the same packages. In some cases these reference unchanged
interfaces/classes which would then be in a different package.
Regards
Carsten
--
Carsten Ziegeler
Adobe
[email protected]
