BrianHotopp b362a0ba91 [2.x] fix: Emit <type> in POM for non-jar explicit artifacts (#8975) ... PomGenerator never emitted <type> for dependencies with explicit artifacts, so a WAR dependency would appear in the POM without <type>war</type>. Maven then treats it as a JAR dependency, resolving the wrong artifact. Uses the primary (non-classifier) artifact to determine the type, so .withSources()/.withJavadoc() classifier artifacts don't produce spurious <type>doc</type> or <type>src</type> elements. Fixes #1979 Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-24 23:51:01 -04:00
..
main	[2.x] fix: Emit <type> in POM for non-jar explicit artifacts (#8975)	2026-03-24 23:51:01 -04:00
test	[2.x] Fix Resolvers test formatting (#8968)	2026-03-23 21:47:42 -04:00