Reconcile making paket package cache working in the same directory as unity’s UPM Packages directory.
In order to separate the Paket nugets from the UPM packages, we rename the UPM package directories to be called after the upm package id's (reverse domain name notation).
Because now the paket nugets and upm packages co-exist, in order to properly do a clean in non-incremental mode, we need to make sure to not delete any of the paket nugets, but also none of the user-preinstalled upm packages that were in unity's Packages/ folder already. We do so by configuration of the paket plugin. It will delete all upm packages from Packages/ folder, EXCEPT the ones defined in paket.preInstalledUpmPackages.
⚠️ NOTE: Special care had to be taken, to make sure that mixing case-sensitive & non-case-sensitive FS & gradle-API works as expected. Tests weren't written to specifically test this however many of the added tests would technically fail in case this would not be handled, and did so during development.
Changes
Support for UPM Packages & Paket nuget cache can share the same location
Installed UPM Embedded Packages use the upm-idiomatic naming convention
Make sure to clean-up uninstalled packages completely in UPM-Embed-mode, including generated package.jsons
Description
Reconcile making paket
packagecache working in the same directory as unity’s UPMPackagesdirectory.In order to separate the Paket nugets from the UPM packages, we rename the UPM package directories to be called after the upm package id's (reverse domain name notation).
Because now the paket nugets and upm packages co-exist, in order to properly do a clean in non-incremental mode, we need to make sure to not delete any of the paket nugets, but also none of the user-preinstalled upm packages that were in unity's
Packages/folder already. We do so by configuration of the paket plugin. It will delete all upm packages fromPackages/folder, EXCEPT the ones defined in paket.preInstalledUpmPackages.⚠️ NOTE: Special care had to be taken, to make sure that mixing case-sensitive & non-case-sensitive FS & gradle-API works as expected. Tests weren't written to specifically test this however many of the added tests would technically fail in case this would not be handled, and did so during development.
Changes