[MASSEMBLY-1022] Unresolved artifacts should be not processed

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.7.1
• Assignee: Slawomir Jaranowski
• Reporter: Slawomir Jaranowski
• Created: 14/Mar/24 21:05
• Updated: 15/Mar/24 07:43
• Resolved: 15/Mar/24 07:43

Description

Bug introduced in: MASSEMBLY-1008

When we filter artifact by scope and resolve dependencies list again with correct score some artifact can be filtered and not resolved in returned dependency tree.

We have artifact with file set to null which cause NPE during including to destination archive.

Issue Links

• fixes: MASSEMBLY-1020 Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null
• fixes: MASSEMBLY-1021 Nullpointer in assembly:single when upgrading to 3.7.0
• is caused by: MASSEMBLY-1008 Assembly plugin handles scopes wrongly
• links to: GitHub Pull Request #194