- 15 Jul, 2015 1 commit
-
-
Releases: master Resolves: #68159 Change-Id: Ic69f454cdb17c16d82aea5d2495b9ae795d600f6 Reviewed-on: http://review.typo3.org/41270 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
-
- 07 Jul, 2015 2 commits
-
-
ext_autoload.php is ignored now, so the issues why we kept this alias in the core is obsolete. Releases: master Resolves: #67966 Change-Id: Ibdcf362b5c31e938941b374aff786d81da4668ba Reviewed-on: http://review.typo3.org/40969 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
Helmut Hummel authored
With class loading information added, we must also add class alias information. Besides that, we need to distinguish between extensions that should be loadable and are part of the framework and those which should only be loaded optionally and are subject to be removed from the core in the near future. These extensions (namely compatibilty6 and mediace) are now made "regular" TYPO3 extensions and class loading information is removed from the main composer.json We now also add the class alias map information to the sub-packages delivered by the core to have a clean state once they are extracted by a subtree split. Having all this in place, we can unify the check for framework extensions in the dependency resolver as well. Releases: 7.3, master Resolves: #67933 Change-Id: I08b576c96921058afcf5e03a7c5c3aa6e25d2d55 Reviewed-on: http://review.typo3.org/40961 Reviewed-by:
Benjamin Mack <benni@typo3.org> Tested-by:
Helmut Hummel <helmut.hummel@typo3.org> Tested-by:
-
- 16 Jun, 2015 1 commit
-
-
Resolves: #67478 Releases: master Change-Id: I49cebb422ff87d245d757f7736a3b8b969e8b243 Reviewed-on: http://review.typo3.org/40273 Reviewed-by:
-
- 10 Jun, 2015 1 commit
-
-
Use composer class loader instead of the TYPO3 class loader when TYPO3 is not installed via composer, thus building the same class information logic during runtime (and caching it away) as composer does with its "dump-autoload" command. Releases: master Resolves: #67212 Change-Id: Id032411a690d67ca690a724748c3c796d2bb5f6e Reviewed-on: http://review.typo3.org/39827 Reviewed-by:
Thomas Maroschik <tmaroschik@dfau.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- 19 May, 2015 1 commit
-
-
Benni Mack authored
The PackageManager was originally backported from Flow but includes too many classes and options that the Core does not use or cannot use at all. The Package code is thus merged with only the parts needed for the TYPO3 Core, and adapted accordingly. All Flow classes are either removed or merged into the needed Package classes of the TYPO3 Core. In order to speed up the bootstrap and prepare for tight composer integration, this task needs to be sorted out first. Next step is to further cleanup code within the Package* classes themselves - things that are not called at all in the TYPO3 Core. Resolves: #67027 Releases: master Change-Id: Ia6823374afa515902e3d5237cef596a440747e3b Reviewed-on: http://review.typo3.org/39518 Reviewed-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
-
- 28 Apr, 2015 1 commit
-
-
Benni Mack authored
Change-Id: Ie9edd14d2d55c1731f69d6f6b15e04e9528efc28 Reviewed-on: http://review.typo3.org/38993 Reviewed-by:
Xavier Perseguers <xavier@typo3.org> Tested-by:
-
- 02 Mar, 2015 1 commit
-
-
The external library RemoveXSS placed within typo3/contrib/ is moved to EXT:core and also loaded via composer in order to avoid a require_once. Additionally, some other changes in the static composer class loader shipped with typo3/contrib/vendor are updated as well. Resolves: #65450 Releases: master Change-Id: I804754df10288924247f58dc93a8e46f9268aa3b Reviewed-on: http://review.typo3.org/37448 Reviewed-by:
-
- 24 Feb, 2015 1 commit
-
-
Wouter Wolters authored
Resolves: #65286 Releases: master Change-Id: I7c8576ebb76bb02582396e1345e253ba0e9a1623 Reviewed-on: http://review.typo3.org/37189 Reviewed-by:
-
- 20 Jan, 2015 1 commit
-
-
Benni Mack authored
Resolves: #64393 Releases: master Change-Id: I3a184047c4af6c9b8656fc78c2d83a0ef3a9f4ec Reviewed-on: http://review.typo3.org/36151 Reviewed-by:
Markus Klein <klein.t3@reelworx.at> Tested-by:
-
- 19 Jan, 2015 1 commit
-
-
Benni Mack authored
In order to deliver more information in custom installations for use with composer, the namespaces for using the composer autoloader are added to each composer.json of all system extensions. Releases: master, 6.2 Resolves: #64356 Change-Id: Ic0fa9e0969a48f68cce8ceeb77dbef3b75e6e6f1 Reviewed-on: http://review.typo3.org/36076 Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
- 03 Dec, 2014 1 commit
-
-
Resolves: #63547 Releases: master Change-Id: I8f48df6de186b416e6a960e8f176afddabb5614d Reviewed-on: http://review.typo3.org/34971 Reviewed-by:
Sebastian Michaelsen <michaelsen@t3seo.de> Tested-by:
-
- 20 Oct, 2014 1 commit
-
-
Update version number of all sysext and dependency definitions. Resolves: #62341 Releases: master Change-Id: Ic8b1b8ead08432917a28b226bbb43347dac42087 Reviewed-on: http://review.typo3.org/33395 Reviewed-by:
-
- 21 Jun, 2014 1 commit
-
-
Resolves: #59742 Releases: 6.3 Change-Id: Id6c05025873bdbdeebd74585f9bd4093657999e0 Reviewed-on: https://review.typo3.org/30965 Reviewed-by: Christian Kuhn Tested-by: Christian Kuhn Reviewed-by: Anja Leichsenring Tested-by: Anja Leichsenring
-
- 15 Mar, 2014 1 commit
-
-
Thomas Maroschik authored
This patch is a combined patch which tries to address the findings from the Bootstrap/PackageManager/ClassLoader performance analysis. Resolves: #56934 Resolves: #56310 Resolves: #56331 Resolves: #56341 Resolves: #56538 Releases: 6.2 Change-Id: I269159906534f58eff59973ab30e170fadac10e4 Reviewed-on: https://review.typo3.org/28329 Reviewed-by: Ernesto Baschny Tested-by: Ernesto Baschny
-
- 03 Mar, 2014 1 commit
-
-
Thomas Maroschik authored
Resolves: #53753 Releases: 6.2 Change-Id: I3acb81c71796bc84ada29e6cdf6141be07f69ca3 Reviewed-on: https://review.typo3.org/25503 Reviewed-by: Christian Opitz Reviewed-by: Fabien Udriot Tested-by: Fabien Udriot Reviewed-by: Felix Kopp Tested-by: Felix Kopp Reviewed-by: Thomas Maroschik Tested-by: Thomas Maroschik
-
- 15 Oct, 2013 1 commit
-
-
The current composer type of system extensions is "typo3cms-framework". In the composer installer for TYPO3 CMS the composer type of extensions is "typo3-cms-extension". In order to align our composer type with the community defined it is changed to "typo3-cms-framework". Resolves: #52831 Releases: 6.2 Change-Id: I1f43a60bd4cf59b47163123b57c8ba09e35e6526 Reviewed-on: https://review.typo3.org/24780 Reviewed-by: Sebastian Fischer Reviewed-by: Christian Kuhn Tested-by: Christian Kuhn
-
- 13 Oct, 2013 1 commit
-
-
Christian Kuhn authored
Change-Id: Iaf88fc46903400d97f6f1dc3acedb3c9b438e8dd Releases: 6.2 Resolves: #52740 Related: #47018 Reviewed-on: https://review.typo3.org/24667 Reviewed-by: Thomas Maroschik Tested-by: Thomas Maroschik Reviewed-by: Alexander Opitz Tested-by: Alexander Opitz Reviewed-by: Christian Kuhn Tested-by: Christian Kuhn
-
