+1 for a myfaces modern or myfaces next, better avoid version numbers
until we know that 3.0 can be finally implemented.
2.3 might be problematic because we have axed legacy functionality which
is known to be axed for 3.0.
Werner
Am 13.12.19 um 10:44 schrieb Thomas Andraschko:
Thanks.
I would avoid 2.4:
1) we currently don't know for 100% what will be the next Jakarta Faces
version
2) its confusing... in OWB we had e.g. OWB 1.2 which implemented CDI
1.0. And OWB 1.7, which implemented CD 1.2.
About the extension:
It's not a normal extension like extcdi or extval. It's more like we had
a GAE support inside myfaces-core.
The difference is that extcdi/extval is just based on EE APIs, whereas
the quarkus extensions has a 1:1 relation to the MyFaces Version + SPI.
I had to adjust many files in MyFaces to make it possible.
I would probably add it here:
https://github.com/apache/myfaces/extensions/quarkus
As i also removed GAE support from core, later we could easily readd it
via a own core extension: https://github.com/apache/myfaces/extensions/gae
Am Do., 12. Dez. 2019 um 21:43 Uhr schrieb Dennis Kieselhorst
<[email protected] <mailto:[email protected]>>:
Thank you for driving this Thomas.
I like releasing early and often but just indicating a completely
refactored version from a different branch with a classifier sounds
confusing for me. Why not using 2.4? There will be no JSF 2.4
version so I don't see any conflict there.
Regarding extension repos: We have repos for myfaces-extcdi and
myfaces-extval. Another additional one for quarkus doesn't hurt, I
can take care of creating it, if you want.
Best,
Dennis
