So if we have a case like: 26.0.0-alpha1, it would create an ItemID like `supportv4-26.0.0-alpha1` which is not allowed. Instead we’ll replace the verison’s - with _ to create `supportv4-26.0.0_alpha1`
Previously the nuspec was changed to use the merge.targets which was incorrect. That file gets merged into the template produced targets to generate Xamarin.Android.Support.Vector.Drawable.targets which is what needs to be packaged into the nuget.
This is the new unifying package which all others depend on in support so that there are no javac errors during app compile due to missing referenced annotations.
This also acts as a version locking unification package for all of support libs, so it should no longer be possible to get versions out of sync (eg: previously you could install a different version of CardView).
There were some initial optimizations done to the adding of —no-version-vectors to AndroidResgenExtraArgs, but they were made to the wrong file. The build script caused the modified file to be overwritten during the build making the changes ineffective.
This commit cleans up where the .targets file lives so the build tasks project reads it from one source, and the build script no longer copies the file around.
We want to start tracking specific cases where we identify issues and try to build some tests around them to avoid future regressions.
This android app will serve as a solution that can be run to perform these tests. Currently it will need to be run manually.
The merge.targets will get merged into the generated .targets file for a given nuget package. This was being gitignored and not properly making it in. This target helps us check the version of android tools installed and adds the —no-version-vectors flag to aapt calls.
Redth