Status Update
Comments
ku...@google.com <ku...@google.com>
gh...@google.com <gh...@google.com> #2
As I understand it, we need to migrate namespace definitions both from AndroidManifest.xml
and from implicit definitions from applicationId
/ testApplicationId
? Is that right? So an 8.0 project would have a
namespace <n>
testNamespace <tn>
where <n> is taken from AndroidManifest.xml
package
definitions if present, and applicationId
if not, and <tn>
is testApplicationId
if present and <n>.test
if not?
gh...@google.com <gh...@google.com> #3
Sorry for the confusion. AGP would change how it computes the namespace for the androidTest variant. All the Upgrade assistant would need to do is update the source code for the import of the R
class.
xo...@google.com <xo...@google.com> #4
OK! And, I think, this should happen at the same time as the namespace
declaration is migrated from AndroidManifest.xml
?
gh...@google.com <gh...@google.com> #5
It's unrelated, but it is possible that we move 8.0 to also only declare the namespace into the DSL. I would make it a separate refactoring because they are not tied at all.
Description
AI-213.7172.25.2113.9123335, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Linux(amd64) v5.17.0-1020-oem, screens 1920.0x1080.0, 2560.0x1440.0
AS: Dolphin | 2021.3.1 Patch 1
Kotlin plugin: 213-1.7.20-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.3.1
Gradle: 7.4
Gradle JDK: version 11.0.13
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
In my build.grade file, I have specified a number of dependencies. In order to ensure that builds don't break when transitive dependencies change, I'm pinning the version of packages to build with. For example, I have:
"implementation 'androidx.appcompat:appcompat:1.5.1!!'"
What is strange is that Android Studio highlights this statement stating:
"A newer version of androidx.appcompat:appcompat than 1.5.1!! is available: 1.5.1"
It appears that the UI is doing a textual string comparison rather than a semantic version comparison. The pinned version is the latest available and should not be highlighted for action.