The CreateAar task was not respecting the Pack='false' metadata on AndroidLibrary items, causing jar files to be included in AAR packages even when explicitly marked for exclusion.

Problem

When using .NET binding projects with AndroidLibrary items set to Pack='false', developers expected the jar files to be excluded from the generated AAR package. However, the CreateAar task was ignoring this metadata and including all jar files regardless of the Pack setting.

This caused issues for developers who wanted to:

• Reference binding projects without packaging the underlying jar files
• Create modular architectures where jars are packaged separately
• Avoid duplicate jar inclusion in complex dependency scenarios

Solution

Modified the jar processing loop in CreateAar.cs to:

• Check the Pack metadata on each jar file item
• Skip jars with Pack='false' using continue;
• Add debug logging for transparency when jars are skipped
• Preserve default behavior (include jars when Pack is unspecified or 'true')

Testing

Added comprehensive test AndroidLibraryPackFalseExcludesJarFromAar that:

• Creates a binding project with both Pack='false' and default Pack jars
• Verifies the AAR is generated successfully
• Examines actual AAR contents to confirm Pack='false' jars are excluded
• Confirms default behavior jars are still included

All existing binding and AAR generation tests continue to pass, ensuring no regressions.

Fixes #8504.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.