Once we can actually invoke Jetifier we'll need to figure out where the appropriate place to 'hook' into the Xamarin.Android msbuild targets is to run Jetifier at.
We have two options for when we Jetify:
First generate ACW and compile against legacy android support jar’s, and run jetifier on everything afterwards (no need to rewrite JNI strings in Register attribute in this scenario)
Compile against new androidx .jar’s and jetify them before ACW generation and compilation (need to rewrite JNI strings in Register attribute)
We are heavily leaning towards option 2. This will require working with probably @dellis1972 and/or @jonathanpeppers to determine the appropriate ItemGroup the .jar files are in which need to be processed, and which targets are best to run this task after/before.
One thing to watch out for here is we may need to keep a black list of android support .jar's that could end up in our item group even though we shouldn't jetify them.
Once we can actually invoke Jetifier we'll need to figure out where the appropriate place to 'hook' into the Xamarin.Android msbuild targets is to run Jetifier at.
We have two options for when we Jetify:
We are heavily leaning towards option 2. This will require working with probably @dellis1972 and/or @jonathanpeppers to determine the appropriate ItemGroup the .jar files are in which need to be processed, and which targets are best to run this task after/before.
One thing to watch out for here is we may need to keep a black list of android support .jar's that could end up in our item group even though we shouldn't jetify them.