[
https://issues.apache.org/jira/browse/MYFACES-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924386#comment-17924386
]
Werner Punz edited comment on MYFACES-4706 at 2/6/25 7:12 AM:
--------------------------------------------------------------
Thats what I am doing in the new codebase, I basically have a function which
resolves the namespace dynamically but also 2 api files which basically are the
main files for each build type so that the codebase is 2.x and 3.x+ compliant
depending on the build, but that was coded in from the ground up. I can add
similar mechanisms in the old codebase, but that would mean some overhaul to
get this functionality in! (not sure how much yet, because the old codebase is
not as well structured as the new one)
The idea why I did this in the new codebase was, that I wanted to replace the
old codebase entirely, but given that we did not do that, the 2.x builds are
only used by the Tobago people atm!
You have to have in mind the javax->jakarta resolution goes deeper, it is not
just the api, but there are some internal calls to the apis to allow them to be
decorated, also there are things like http parameters etc...
I can give it a shot though and apply the same idea which works on the new
codebase on the old one, but that basically means we will do deeper changes on
the 2.x codebase instead of just fixes!
was (Author: werpu):
Thats what I am doing in the new codebase, I basically have a function which
resolves the namespace dynamically but also 2 api files which basically are the
main files for each build type so that the codebase is 2.x and 3.x+ compliant
depending on the build, but that was coded in from the ground up. I can add
similar mechanisms in the old codebase, but that would mean some overhaul to
get this functionality in! (not sure how much yet, because the old codebase is
not as well structured as the new one)
The idea why I did this in the new codebase was, that I wanted to replace the
old codebase entirely, but given that we did not do that, the 2.x builds are
only used by the Tobago people atm!
You have to have in mind the javax->jakarta resolution goes deeper, it is not
just the frontend api, but there are some internal calls to the front apis to
allow them to be decorated, also there are things like http parameters etc...
I can give it a shot though and apply the same idea which works on the new
codebase on the old one, but that basically means we will do deeper changes on
the 2.x codebase instead of just fixes!
> Sync jsf.js code between 2.3 and 3.0
> ------------------------------------
>
> Key: MYFACES-4706
> URL: https://issues.apache.org/jira/browse/MYFACES-4706
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 3.0.2
> Reporter: Volodymyr Siedlecki
> Assignee: Werner Punz
> Priority: Major
>
> MYFACES-4522 synced up the javascript code between 2.3 and 2.3-next.
> However, 2.3 and 3.0 branches are basically the same. Therefore, the changes
> to 2.3 should be applied to 3.0. Support-wise, it would be easier since
> they would share the same code base.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
