Lenny Primak
Lenny Primak
It's auto-relocation of all versions > X instead of manually having to publish each relocation separately. Just a bit of automation. Relocations (I believe) show up in maven central just...
Users typically will *not* look at the contents of the stuff. They will just ask "what's the latest" and it'll show up as both GA. This will cause confusion.
Romain, the relocated is only for "microprofile:microprofile:pom" artifact, which will contain only the APIs that are proper for the correct version, so this is OK
This is what I do: ``` lprimak@Lennys-Mac-Nov-2024 ~ % mcs search ant:ant Searching for ant:ant... Found 13 results Coordinates Last updated =========== ============ ant:ant:1.7.0 20 Jan 2008 at 18:40 (CST)...
Also maybe tools like dependabot or maven versions plugin should look at the latest version, check if it's a relocation and check that for newer versions. I personally thought that...
Oh trust me, I still want to get rid of warnings. For this type of relocation (auto-relocate) I would not want any kind of warnings.
CORBA and remote EJBs have not been supported on JDK > 21 for a while now. I think there is another issue for this sitting in the Payara internal JIRA
Will this fix #7436 ?
Hmmm. I am confused. From the docs on https://omnifaces.org: `OmniFaces 5.x requires Java 17, Faces 4.1, EL 6.0, Servlet 6.1, CDI 4.1, WS 2.2` According to this, OmniFaces 5.s is...
In the home page, maybe you should changes Faces 4.1 -> `Faces 5.0` for OmniFaces 5.x, and change `Faces 3.0` -> `Faces 3.0, Faces 4.0` for OmniFaces 4.x. That would...