Along with that we simply need to have a cli parameter and an option in nativescript.config

# Conflicts:
#	lib/services/plugins-service.ts

fix: require.resolve for packages with exports field in package.json

see https://www.mobileit.cz/Blog/Pages/r-class.aspx

can still be enabled with `generateBuildConfig` and `generateR`

# Conflicts:
#	lib/services/log-source-map-service.ts
#	lib/services/metadata-filtering-service.ts
#	lib/services/test-execution-service.ts
#	vendor/gradle-plugin/build.gradle

# Conflicts:
#	lib/services/android-plugin-build-service.ts
#	vendor/gradle-plugin/build.gradle

and other gradle scripts

# Conflicts:
#	lib/commands/plugin/build-plugin.ts
#	lib/data/build-data.ts
#	lib/declarations.d.ts
#	lib/definitions/android-plugin-migrator.d.ts
#	lib/definitions/build.d.ts
#	lib/options.ts
#	lib/services/android-plugin-build-service.ts
#	lib/services/android-project-service.ts
#	lib/services/android/gradle-command-service.ts
#	yarn.lock

…es for `run|debug`

this passes a gradle `abiFilters` arg to the build process which could allow the gradle config to only build abis of connected devices.
* build faster
* could be used with split to only deploy a smaller apk to each device depending on its abi

Default to false for now. Could become the default later

It requires an update to the gradle file in the android runtime

This allow a Nativescript plugin to depend on another nativescript native plugin code

# Conflicts:
#	lib/definitions/android-plugin-migrator.d.ts
#	lib/services/android-plugin-build-service.ts
#	lib/services/android-project-service.ts
#	lib/services/ios-project-service.ts
#	vendor/gradle-plugin/build.gradle

* copy paste for now. I think most could be refactored in the runtime and cli should include from there
* not kotlin, buildtools, … versions are define like in apps and use same defaults
* we dont modify the build.gradle for tempPlugin anymore. Instead we add the plugin as a native dep (to itself..) and just ignore the `aar` that we would build (which can already be there).
* now users can do almost anything they want in their plugin `include.gradle` and it will work (for example comments on the first line would break the build)
* now while building a tempPlugin we pickup any external aar we find the plugin `platforms` folder (main reason for this change)

…ling'

….git

# Conflicts:
#	lib/base-package-manager.ts
#	lib/controllers/build-controller.ts
#	lib/nativescript-cli.ts
#	lib/package-installation-manager.ts
#	lib/package-manager.ts
#	lib/services/android-plugin-build-service.ts
#	lib/services/device/device-install-app-service.ts
#	lib/services/timeline-profiler-service.ts
#	lib/yarn2-package-manager.ts
#	package-lock.json
#	package.json
#	yarn.lock

# Conflicts:
#	lib/base-package-manager.ts
#	lib/controllers/build-controller.ts
#	lib/nativescript-cli.ts
#	lib/package-installation-manager.ts
#	lib/package-manager.ts
#	lib/services/android-plugin-build-service.ts
#	lib/services/device/device-install-app-service.ts
#	lib/services/timeline-profiler-service.ts
#	lib/yarn2-package-manager.ts
#	package-lock.json
#	package.json
#	yarn.lock

# Conflicts:
#	lib/controllers/build-controller.ts
#	lib/services/device/device-install-app-service.ts
#	package-lock.json
#	yarn.lock

…nfig (`android.gradleVersion`).

Also we now replace `{{pluginNamespace}}` for plugins as requirement for gradle 8
Same `__PACKAGE__` is replaced in app build.gradle (for namespace or app id)

…ency on runtime update

…o platforms/android. Those must be modules like AndroidTest or benchmark

…id module

Still a lot of work to be done there

…s and app

…d to rebuild for devices we are building for

It requires a PR on @nativescript/webpack too

…eeded