- Jul 06, 2023
-
-
Andreas Nedbal authored
This patch adds support for loading the base CKEditor 5 locales and importing them in the backend if requested. Because CKEditor doesn't ship a full set of locales, we needed to add an additional build step that assembles the locales of all plugins we have installed. Resolves: #100873 Releases: main, 12.4 Change-Id: I971bf3e55d006a4a378123e8723c1bb8d23b09d1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79777 Tested-by:
Andreas Nedbal <andy@pixelde.su> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
-
- Mar 14, 2023
-
-
jakotadesigngroup authored
Resolves: #100131 Releases: main, 11.5 Change-Id: If23bfd25f95b328bee8227003e7983ef17f61dfb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78083 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Chris Müller <typo3@krue.ml> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- Oct 14, 2022
-
-
Stefan Bürk authored
JetBrains created a new product named `Fleet` as lightweight editor. This tool tends to write it's config files to `.fleet/` folders, like all of the IntellJ based IDE's like PHPStorm uses the `.idea` folder. This change adds this config folder to .gitignore to avoid adding this folder to a patch if `Fleet` is used to create a patch. Resolves: #98615 Releases: main, 11.5, 10.4 Change-Id: I4f629a37904c2e9fda57df830377c98a88bec69c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76115 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
-
- Oct 01, 2022
-
-
Benni Mack authored
Composer-based installations will now have their extensions within composers' vendor folder instead of typo3/sysext/ and typo3conf/ext/. This way, all non-public files are moved outside the document root (ideally), while public files within extensions are symlinked to public/_assets/. TYPO3 will then resolve "EXT:" syntax depending on public / private folders to their respective locations. Used commands: - composer req "typo3/cms-composer-installers:^5.0" - composer req "typo3/cms-composer-installers:^5.0" --no-update -d typo3/sysext/core Resolves: #98484 Releases: main Change-Id: Ia790e9e306ec142a0c581b801936d6b2c36e5c46 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75917 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
- Sep 06, 2022
-
-
Benjamin Franzke authored
`unsafe-perm = true` is not available in npm v8 documentation, and TYPO3 core requires npm =>v8. The file has been introduced with #96355 during yarn to npm migration, it has been added during early patchsets that targeted npm v6. Now that we use npm v8 it is no longer needed. Releases: main Resolves: #98270 Related: #96355 Change-Id: Ide7eea24f6b78da2f83a8d6303021e734bdcb47b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75625 Tested-by:
-
- Aug 23, 2022
-
-
Benjamin Franzke authored
Yarn has been added to TYPO3 back in 2017 because npm shrinkwrap files were not stable and package-lock.json and `npm ci` not yet established. By now the yarn version in TYPO3 (v1) got outdated and an update to yarn v3 would be required sooner or later. The update to yarn v3 brings quite some problems for the TYPO3 codebase: - Yarn v3 is executed/proxied through yarn v1 (installed on the developer machine) – therefore the yarn v3 executable needs to be tracked within git. See https://yarnpkg.com/cli/set/version#details - Yarn v3 pulls in @types/node (through the "got" package) for unknown reasons, causing clashes with TypeScript declarations for requirejs (window.require vs node's require()) As package-lock.json is solid thesedays, there is no real need to depend on yarn anymore. We basically switch to npm because that switch is way more straightforward than migrating to yarn v3 and it removes one dependency. Note that `npm install` properly honors `package-lock.json` these days (no implicit version upgrades due to the lock file), but is faster than `npm ci`, therefore it is used in `grunt build` and runTests.sh for all developer oriented build-targets. All CI checks use `npm ci` to enfore a clean install. We set the required npm verson to v8 in order to use the newest package-lock.json v3 format and .nvmrc is updated to suggest the recent nodejs v16 LTS release, as npm v8 is shipped with nodejs v16 by default. Note that node v14 may still be used to compile packages, but npm v8 is needed for dependency installation (installable via `npm install -g npm` in node v14 installations). For that reason the CI docker images are updated to use nodejs v16 instead of nodejs v14, see following ticket for details: https://git.typo3.org/typo3/CI/testing-infrastructure/-/issues/3 Executed Commands: cd Build/ # be sure the node_modules folder dir and is updated yarn install sed -i 's/"yarn": "^1.22.0"/"npm": ">=8.0.0 <9.0.0"/' package.json rm -f package-lock.json # npm install >= v7 can read yarn.lock and will create # package-lock.json as a result npm install git add package-lock.json git rm -f yarn.lock npm remove "jquery-ui" # The use of `git@` in the HTTPS URLs is a workaround for NPM's # auto-rewrite that results in an SSH URL being used instead, # which fails to install in CI. # See npm/cli#2610 for more information. npm install "git+https://git@github.com/jquery/jquery-ui#1.11.4" # Fix fsevents not being installed npm install rollup@~2.32.0 # Explicitly pull in popperjs which would be included by npm's # resolver in npm >8.5 npm install @popperjs/core@^2.11.6 # Let npm build a new, fully clean tree, without old yarn cruft rm -rf node_modules/ npm install grunt default Resolves: #96355 Related: #83038 Releases: main Change-Id: I88c1ecb1b12dcd117ac4200307af72d330c76d27 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72642 Tested-by:
-
- Jul 31, 2022
-
-
Stefan Bürk authored
Codeception released new major version 5, which unblocks upgrading to symfony 6 components. This patch raises codeception only, thus acting as a pre-patch to raise symfony requirements. Codeception 5 is hard to impossible with core v11, so this patch is v12 only: Codeception 5 requires PHP 8.0, so we'd have to support both 4 and 5 in v11 to allow testing with older PHP versions. This would result in various headaches since some API changes in codeception 5 are hard breaking in PHP, especially due to changed class property type hints. We'll thus keep codeception 4 in v11 and go with codeception 5 in v12. Minor acceptance test related adaptions are needed: * Replaced config option `path.log` with `path.output` * Added proper property type because of inheritance to codeception setup classes * Ensure method return type compatibility * Use `actor`instead of `class name` in suite config * Create acceptance split files in proper folder to ensure group filtering keeps working. Adjust clean up scripts and gitignore for this Used commands: > composer req --dev -w \ typo3/testing-framework:dev-main \ codeception/codeception:^5.0.0 \ codeception/module-asserts:^3.0.0 \ codeception/module-cli:^2.0.0 \ codeception/module-filesystem:^3.0.0 \ codeception/module-webdriver:^3.1.2 \ codeception/lib-asserts:^2.0.0 Resolves: #98047 Releases: main Change-Id: I5cea60c2641988cc032b30ed1fbe3d8b0ed3b3d1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75317 Tested-by:
-
- Oct 19, 2021
-
-
Christian Kuhn authored
phpunit has a default-enabled feature to write test result to a cache file. phpunit however has no option to only run failed tests since those tests may have an @depends annatation and its hard for phpunit to sort this out. The cache file is of rather little use and mostly only pollutes the filesystem in real life. When developing core tests, developer typically use a filter or a path constraint to execute a sub set of tests only. Additionally, with multiple phpunit .xml files in one directory, the cache file overrides itself when different suites are executed. The patch disables that cache file by default in phpunit xml files. If anyone still wants to run the test suite and have tests that failed executed first, the option can be enabled on a per-use basis, example using runTests.sh: # Run suite and create cache file Build/Scripts/runTests.sh -e '--cache-result' # Run tests that failed first and update cache file Build/Scripts/runTests.sh -e '--cache-resul...
-
Jochen Roth authored
To make sure the sitemap works as expected a acceptance test has been added for the sitemap overview and detail view. Resolves: #94903 Releases: master Change-Id: Ia747e4103aec5678300c0f91721bbef14e27e1d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70639 Tested-by:
-
- Aug 13, 2021
-
-
Wouter Wolters authored
diff-format option has been removed. udiff is the default now since v3. composer u friendsofphp/php-cs-fixer composer/xdebug-handler php-cs-fixer/diff composer req --dev friendsofphp/php-cs-fixer:^3.0 Resolves: #94856 Releases: master Change-Id: I33470fc49b4355130e73326c85323a1848fe3562 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70516 Tested-by:
-
- Aug 06, 2021
-
-
Christian Kuhn authored
typo3/testing-framework ships default .xml and bootstrap files for phpunit unit and functional tests. They are however quite hard to maintain since the testing-framework supports multiple core versions at once, but core occassionally needs version specific settings. The patch copies the files from the testing-framework to Build/phpunit and adapts core usages. The files within testing-framework will be kept, but will receive an additional "these are boilerplates, consider copying them to your extension" hint for extension developers. The local .xml files are now: * Compatible with phpunit 9 * Let tests fail if phpunit marks a test with warning. With this enabled, we would have seen the issues fixed with #94724 and #94723 with initial #94706 already. Good to do that now. Resolves: #94725 Related: #94706 Related: #94723 Related: #94724 Releases: master Change-Id: I9fef75a972759d26d4e0e3286142cacf181c33d2 Reviewed-on: https://review.typo3.org/c/Pack...
-
- Feb 24, 2021
-
-
Christian Kuhn authored
The acceptance and functional test splitter scripts from typo3/testing-framework are tailored for core specific needs and of rather little use for non-core. For the sake of a more clean typo3/testing-framework, the patch merges the scripts into core mono-repo. Change-Id: Iefb576bb52c238ccca7b618fa6f9ea0d5718d0f9 Resolves: #93586 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68098 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
- Feb 15, 2021
-
-
Jochen Roth authored
Check for user in /etc/passwd, if it does not exist create a temporary passwd to get values from. Resolves: #93372 Releases: master, 10.4, 9.5 Change-Id: I60c9d2a10a0da155354546d57c823961bc39f014 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67539 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
-
- Jan 25, 2021
-
-
Christian Kuhn authored
The '-c x/y' option for acceptance and functional jobs now allows to split the set of acceptance/functional tests into chuncks just like the CI does to share resources between multiple parallel jobs. Adding this to runTests.sh allows to replay the exact same list of tests that CI does. This example will execute tests of chunk 3 from 10 chunks with mariadb and php 7.4: Build/Scripts/runTests.sh -s functional -d mariadb -p 7.4 -c 3/10 Resolves: #93361 Releases: master, 10.4, 9.5 Change-Id: I5753a8f83a3ebec6823cb0b44d4ca35f3a64055f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67526 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Christian Kuhn <lolli@schwarz...>
-
- May 26, 2020
-
-
Thomas Pronold authored
In order to avoid accidentally committing a FIRST_INSTALL for developers starting to contribute to TYPO3 Core and using Core git repository for its basis local development setup, the FIRST_INSTALL file is ignored from git. Resolves: #91119 Releases: master, 10.4, 9.5 Change-Id: Iad459240bbc8a68892f03adf547373bc608f6a90 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64239 Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
-
- Apr 05, 2019
-
-
Andreas Fernandez authored
TypeScript: Due to issues with upcoming TypeScript versions, the TypeScript sources are moved into the Build directory before building JavaScript. The unused Grunt task `tsdev` has been removed. Additionally, some type defintions have been installed: yarn add --dev \ @types/bootstrap-slider \ @types/datatables.net \ @types/chosen-js Sass: The Sass sources have been moved into the common "Sources" directory. Those source files are moved to have a less cluttered Build directory. Note: With this patch, all TypeScript files must be placed into `Build/Sources/TypeScript` to be compiled by tsc again. Resolves: #88043 Releases: master Change-Id: I4d3e5f69564c38a35bf083652ea7262f5b85e4f3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60335 Tested-by:
-
- Oct 25, 2018
-
-
Christian Kuhn authored
The patch adds a new entry script Build/Script/runTests.sh that hides away all the complexity of test suite execution and docker details to execute everything that bamboo performs locally via docker. Use Build/Script/runTests.sh -h for an overview of available options. Example call to execute all functional tests on postgres DBMS and sending xdebug output to a local (phpstorm) listening on port 9000: Build/Script/runTests.sh -s functional -d postgres -x Change-Id: Idaaf0a90ed1a0ba0f31c1b7128dd9d564335e056 Resolves: #86746 Releases: master Reviewed-on: https://review.typo3.org/57789 Reviewed-by:
Joerg Kummer <typo3@enobe.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Sybille Peters <sypets@gmx.de> Tested-by:
Jonas Eberle <flightvision@googlemail.com> Tested-by:
-
- Sep 18, 2018
-
-
Josef Glatz authored
This patch adds .log files to .gitignore. Releases: master Resolves: #86302 Change-Id: If19c37208fb6d2d7004a03daca8d58821f2fae42 Reviewed-on: https://review.typo3.org/58321 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- Aug 10, 2018
-
-
Sybille Peters authored
Add directory created by documentation rendering to .gitignore. Rendering the docs locally is helpful for checking if it will render correctly on the server. This will create the rendered files in typo3/sysext/*/Documentation-GENERATED-temp/. Adding this to .gitignore will prevent accidentally adding the generated documentation to a patch. Resolves: #85725 Releases: master, 8.7 Change-Id: Ibcff2570b961e1f1add519ead49e565c671a28ba Reviewed-on: https://review.typo3.org/57771 Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
- Jul 07, 2018
-
-
Davert authored
typo3/testing-framework got a major release: composer update typo3/testing-framework ^4.0 * codeception acceptance tests now live in a proper php namespace * merged installation suites yml files into one * installer tests are now one suite with different environment settings * aligned with changes in typo3/testing-framework * renamed Acceptance test suite to Backend test suite * removed Admin/Editor steps, replaced with useExistingLogin('role') Resolves: #85472 Releases: master Change-Id: Ia049b43f5f9f645dddb509bde557ad83a7ac9023 Reviewed-on: https://review.typo3.org/57461 Tested-by:
-
- Jun 22, 2018
-
-
Harry authored
Resolves: #85324 Releases: master, 8.7, 7.6 Change-Id: I90461715f59cd74c72571151f3e37cb4ee374b7f Reviewed-on: https://review.typo3.org/57280 Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
-
- Aug 14, 2017
-
-
Philipp Gampe authored
Make sure root level excludes are prefix with a forward slash (/). The /bin folder exclude is already fixed by a previous commit in master. Sort the .gitignore into logical groups. Releases: 7.6, 8.7, master Resolves: #81992 Change-Id: If1cb4105e57fb7ab3c28448abc3eaeb898da60e3 Reviewed-on: https://review.typo3.org/53612 Reviewed-by:
Henning Liebe <h.liebe@neusta.de> Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
- Jul 31, 2017
-
-
Helmut Hummel authored
With the new composer installers versions, the core package itself (in fact any composer package) can add scripts to be run on composer build time. Use this API to add scripts to TYPO3, that will create the entry scripts for frontend, backend and install tool We do this in a way, that also works if these system extensions are installed individually. This also has the benefit, that we can adapt the core with doing more things during composer build time (e.g. maybe publishing assets) in the future, or change the entry scripts to different locations, without touching the plugin any more. Resolves: #81981 Releases: master Change-Id: I3982bd5e73a14cdd54e83d0a7b3a1c93f2191efd Reviewed-on: https://review.typo3.org/53602 Reviewed-by:
-
- May 20, 2017
-
-
Christian Kuhn authored
The components/ directory has been a temporary directory in v8 phase, does not exist anymore and can be removed from .gitignore. Change-Id: I0f690c8fb38733dc8d168a7e43078dffc60450ea Resolves: #81286 Releases: master, 8.7 Reviewed-on: https://review.typo3.org/52881 Tested-by:
-
- Feb 05, 2017
-
-
Christian Kuhn authored
Change-Id: I0660bddb5411c8b02fe2cf2e285343f90f49e4d9 Resolves: #79631 Related: #79518 Releases: master Reviewed-on: https://review.typo3.org/51541 Tested-by:
-
- Jan 27, 2017
-
-
Georg Ringer authored
The php-cs fixer creates a cache file which should not be commited. Add it to the .gitgnore to avoid any mistakes. Resolves: #79510 Releases: master, 7.6 Change-Id: Ia85f825416ad767a07d280de35a18c318e1a5133 Reviewed-on: https://review.typo3.org/51441 Reviewed-by:
Thomas Hohn <thomas@hohn.dk> Tested-by:
-
- Nov 07, 2016
-
-
Mathias Brodala authored
This moves the toplevel "index.php" to the frontend extension as "frontend.php". The toplevel "index.php" becomes a stub which includes the "frontend.php". This setup works in the following cases: 1) Package "typo3/cms" is the root package 2) The "index.php" is symlinked into the web-dir 3) The "index.php" is copied into the web-dir In all of these cases "typo3" is a toplevel directory. Resolves: #73027 Releases: master Change-Id: I1c0653bcc4691105eb2ccfbea2bcc873ce6189da Reviewed-on: https://review.typo3.org/46390 Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
-
- Oct 24, 2016
-
-
Frank Naegler authored
This patch removes *.js.map files from the repository and adds a new rule to the .gitignore file. Resolves: #78407 Releases: master Change-Id: I227dc1748a0b53910d7fc2050ccf92bfd555d4ec Reviewed-on: https://review.typo3.org/50348 Reviewed-by:
Patricia Tiedemann <pixelaeffchen@googlemail.com> Tested-by:
-
Frank Naegler authored
Resolves: #78389 Releases: master Change-Id: Ic022f1a19859cf48d92a1e50d45327c42ea7be21 Reviewed-on: https://review.typo3.org/50335 Tested-by:
Michael Oehlhof <typo3@oehlhof.de> Tested-by:
-
- Oct 10, 2016
-
-
Frank Naegler authored
This patch introduce a grunt TypeScript processor and linter. Resolves: #77900 Releases: master Change-Id: I642db25c84946a97687e1aaa9e1c5e0599618073 Reviewed-on: https://review.typo3.org/49895 Tested-by:
Marco Bresch <marco.bresch@starfinanz.de> Reviewed-by:
-
- Jun 08, 2016
-
-
Wouter Wolters authored
There is a comment in the .gitignore file to report any changes to this file into a Forge issue. Till now nobody did that. Remove this useless comment now. Resolves: #76510 Releases: master Change-Id: If5dc0193c85f904fd7a038ee9cf6ceb4c98661da Reviewed-on: https://review.typo3.org/48494 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Morton Jonuschat <m.jonuschat@mojocode.de> Tested-by:
-
- Mar 03, 2016
-
-
Anja Leichsenring authored
Resolves: #74011 Releases: master Change-Id: If536bd1bbfe21cd015195eb38ade876460defb31 Reviewed-on: https://review.typo3.org/47009 Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
-
- Aug 11, 2015
-
-
Helmut Hummel authored
The typo3/ directory must currently be exposed in the web root for TYPO3 to work properly. Having the vendor dir with all composer dependencies in typo3/vendor however means, that these will also be exposed. This can be a security risk, which can be avoided by simply moving the vendor directory one level up. By doing so, a web directory which contains only two symlinks (typo3 and index.php) and no sources or link to the sources, will be protected from this risk. Resolves: #68918 Releases: master Change-Id: I5e504520102f94c81897945b41043d930cfc5b5f Reviewed-on: http://review.typo3.org/42495 Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
-
- Jul 16, 2015
-
-
Markus Klein authored
The composer.lock should be shipped in order to ensure correct versions of dependencies on source checkouts. Additionally it ensures that the tests are based on the same versions (of all recursive dependencies). More details are added to the forge ticket. Resolves: #59515 Releases: master Change-Id: Id4d0d5a34a6cce1315089239593143fcdc25e274 Reviewed-on: http://review.typo3.org/39971 Reviewed-by:
Helmut Hummel <helmut.hummel@typo3.org> Tested-by:
-
- Jul 15, 2015
-
-
Christian Kuhn authored
typo3/contrib contains only vendor directory handled by composer. Move vendor one directory up to finally get rid of contrib/. Resolves: #68181 Releases: master Change-Id: I0f579b41db685339fb10b1c7d14bc99ca6fea0b1 Reviewed-on: http://review.typo3.org/41317 Reviewed-by:
-
Georg Ringer authored
A first acceptance test is added to check if the backend login form is displayed. To be able to run tests, you need to follow this steps: * composer update * Build the required tester: ./bin/codecept build -c typo3/sysext/core/Build/AcceptanceTests.yml * Start a local web server: php -S localhost:8000 & * Run the test suite ./bin/codecept run acceptance -c typo3/sysext/core/Build/AcceptanceTests.yml typo3/sysext/core/Tests/Acceptance Change-Id: I06eae24f8356c05e083f268326ea8f9563df6b74 Resolves: #68114 Releases: master Reviewed-on: http://review.typo3.org/41262 Reviewed-by:Susanne Moog <typo3@susannemoog.de> Tested-by:
-
- Apr 02, 2015
-
-
Markus Klein authored
* Group ignores by purpose * Ignore .htaccess only on top-level Resolves: #66229 Releases: master, 6.2 Change-Id: I4855caa6b2986cd358bf7d77fded31ea8465320a Reviewed-on: http://review.typo3.org/38426 Reviewed-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
Xavier Perseguers <xavier@typo3.org> Reviewed-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
-
- Mar 28, 2015
-
-
Benjamin Mack authored
The bower components needed for building the development setup are now downloaded under Build/bower_components, so no adaption is needed in the bower configuration anymore. This makes the directory "typo3/" to only contain the necessary files to deploy the sources at a development machine, as the required files are copied to typo3/sysext/core/Resources/Public/JavaScript/Contrib and commited. Additionally, a README.txt is put in the Contrib/ directory to notify developers that the files should not be referenced manually. The prototype.js and bootstrap.js libraries are moved to the Contrib/ directory and their references are changed accordingly. Resolves: #66108 Releases: master Change-Id: Iaa0554779a317a4dcd4eb853e86a8e6459dffe58 Reviewed-on: http://review.typo3.org/38319 Reviewed-by:
Daniel Sattler <sattler@b13.de> Tested-by:
Andreas Fernandez <andreas.fernandez@aspedia.de> Tested-by:
-
- Mar 26, 2015
-
-
Benjamin Mack authored
Introduce "bower" as a component dependency management for loading all JS/CSS related libraries. This patch introduces bower to install web-related components into EXT:core/Resources/Contrib/components/ which is excluded from the Git Repository. The main LESS file of t3skin, which is currently the only place where the current third-party library (previously from composer) were used. The code is adapted accordingly. The new file .bowerrc holds the information where to install the components, bower.json contains the dependencies needed. Currently there are only development-related components in bower.json. For more information about bower see http://bower.io. Resolves: #66042 Releases: master Change-Id: I4ee7e7a5a47d39a3c66c674556e59643d0ff2336 Reviewed-on: http://review.typo3.org/38238 Reviewed-by:
-
- Mar 25, 2015
-
-
Benjamin Mack authored
In a result of best practices with composer as well as taking the tarball distributions (typo3_src.zip) into account, the directory Packages/ is not necessarily optimal now for either development and shipping a package. Distributions (like the composer-installer for TYPO3) can still use the Packages/ directory in their webroot for other packages. This means: The TYPO3 source will not contain any third party library anymore in its GIT repository but instead these are installed via composer. For development purposes this means that a "composer install" command will install all required dev-dependencies into typo3/contrib/vendor/ which is now ignored by git and no changes are installed anymore. For the packaging process a "composer install --no-dev -o" will be executed when building the tarball and zip files on each release, downloading the necessary third-party libraries directly into "typo3/contrib/vendor/". Existing developer installations need to run "rm -rf typo3/contrib/vendor/ bin/ Packages/Libraries/ composer.lock" inside the typo3 repository directory and do a "composer install" again after applying this patch. This way, there is no conflict between autoloader as well as the Packages/ directory anymore for the TYPO3 CMS Core. The typo3/contrib/vendor/ folder is completely removed from Git as it is now handled via composer. Resolves: #66001 Releases: master Change-Id: I70ff4e1427f2b9d888b7de336e577851116b93cf Reviewed-on: http://review.typo3.org/38138 Reviewed-by:
Markus Klein <klein.t3@reelworx.at> Tested-by:
-
