Skip to content

[Xamarin.Android.Build.Tasks] Restore @(AndroidEnvironment) - #742

Merged
jonpryor merged 1 commit into
dotnet:masterfrom
jonpryor:jonp-resolve-cached-env
Aug 11, 2017
Merged

[Xamarin.Android.Build.Tasks] Restore @(AndroidEnvironment)#742
jonpryor merged 1 commit into
dotnet:masterfrom
jonpryor:jonp-resolve-cached-env

Conversation

@jonpryor

Copy link
Copy Markdown
Contributor

We have a failure within
EnvironmentTests.EnvironmentVariablesFromLibraryProjectsAreMerged
(commit ea6b9b4): the @(AndroidEnvironment) from the library
project is not merged into the App .apk:

Expected: null
But was: "Well, hello there!"

(The arguments were in the wrong order. Oops.)

The cause for this is due to <ResolveLibraryProjectImports/>
attempts to avoid duplicate work; from the build log

Task "ResolveLibraryProjectImports"
Assemblies:
.../xamarin-android/bin/TestDebug//LibraryResources.dll
Skipped resource lookup for .../xamarin-android/bin/TestDebug/LibraryResources.dll: extracted files are up to date
ResolvedEnvironmentFiles:

BecauseLibraryResources.dll was skipped, the
@(AndroidEnvironment) entries from LibraryResources.dll were also
skipped! Doh!

Update the <ResolveLibraryProjectImports/> task so that when
resource extraction for an assembly is skipped, we remember to add the
already-extracted @(AndroidEnvironment) values.

We have a failure within
`EnvironmentTests.EnvironmentVariablesFromLibraryProjectsAreMerged`
(commit ea6b9b4): the `@(AndroidEnvironment)` from the library
project is not merged into the App `.apk`:
Expected: null
But was: "Well, hello there!"
(The arguments were in the wrong order. Oops.)
The cause for this is due to `<ResolveLibraryProjectImports/>`
attempts to avoid duplicate work; [from the build log][0]
[0]: https://jenkins.mono-project.com/view/Xamarin.Android/job/xamarin-android/526/consoleText
Task "ResolveLibraryProjectImports"
Assemblies:
.../xamarin-android/bin/TestDebug//LibraryResources.dll
Skipped resource lookup for .../xamarin-android/bin/TestDebug/LibraryResources.dll: extracted files are up to date
ResolvedEnvironmentFiles:
*Because* `LibraryResources.dll` was skipped, the
`@(AndroidEnvironment)` entries from `LibraryResources.dll` were also
skipped! Doh!
Update the `<ResolveLibraryProjectImports/>` task so that when
resource extraction for an assembly is skipped, we remember to add the
already-extracted `@(AndroidEnvironment)` values.
@jonpryorjonpryor mentioned this pull request Aug 11, 2017
@jonpryor
jonpryor merged commit 8a703c6 into dotnet:masterAug 11, 2017
jonpryor added a commit that referenced this pull request Aug 11, 2017
We have a failure within
`EnvironmentTests.EnvironmentVariablesFromLibraryProjectsAreMerged`
(commit ea6b9b4): the `@(AndroidEnvironment)` from the library
project is not merged into the App `.apk`:
Expected: null
But was: "Well, hello there!"
(The arguments were in the wrong order. Oops.)
The cause for this is due to `<ResolveLibraryProjectImports/>`
attempts to avoid duplicate work; [from the build log][0]
[0]: https://jenkins.mono-project.com/view/Xamarin.Android/job/xamarin-android/526/consoleText
Task "ResolveLibraryProjectImports"
Assemblies:
.../xamarin-android/bin/TestDebug//LibraryResources.dll
Skipped resource lookup for .../xamarin-android/bin/TestDebug/LibraryResources.dll: extracted files are up to date
ResolvedEnvironmentFiles:
*Because* `LibraryResources.dll` was skipped, the
`@(AndroidEnvironment)` entries from `LibraryResources.dll` were also
skipped! Doh!
Update the `<ResolveLibraryProjectImports/>` task so that when
resource extraction for an assembly is skipped, we remember to add the
already-extracted `@(AndroidEnvironment)` values.
@github-actionsgithub-actionsBot locked and limited conversation to collaborators Feb 5, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@jonpryor@dellis1972@dnfclas