93531[WIP][BUGFIX] Disarm `ext_emconf.php` deprecation for functional tests
Commit message
Review
-
Code review CR -2
- Helmut Hummel -2
-
Verified V 0
- core-ci +1 CI
Issues 3
Files 1
Review log 810
-
Stefan Bürk uploaded patch set 1 04/03/26, 00:21
-
core-ci voted on patch set 1 V +1 04/03/26, 00:32 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/99526
-
Stefan Bürk uploaded patch set 2
V +104/03/26, 01:34 -
core-ci voted on patch set 2 V +1 04/03/26, 01:44 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/99530
-
Helmut Hummel commented on patch set 2 CR -1 04/03/26, 11:06
I do not think this solves anything to hide the deprecation message conditionally -
Helmut Hummel commented on patch set 2 04/03/26, 11:15
The deprecation message enforces nothing! TYPO3 classic mode enforces a version to be set. End of story. We have multiple options to deal with this requirement: 1. ignore it, liften this requirement and and make EM dependency resolving of EM less useful than it currently is. 2. Keep the ext_emconf.php file forever 3. Introduce a new file to store the version in 4. Store the version in a different field https://review.typo3.org/c/Packages/TYPO3.CMS/+/93536 I personally don't like any of these alternatives, but I could live with 4. (hence I proposed the change) -
Helmut Hummel voted on patch set 2 CR -2 04/03/26, 12:33
-
Stefan Bürk commented on patch set 2 04/07/26, 10:10
Reply
Done -
Stefan Bürk abandoned the change 04/07/26, 10:10
in favour of 93536: [TASK] Allow extension version declaration in extra.version | https://review.typo3.org/c/Packages/TYPO3.CMS/+/93536 -
Stefan Bürk commented on patch set 2 04/07/26, 10:10
Reply
Done