Skip to content

[MASSEMBLY-1022] Unresolved artifacts should be not processed #1234

@jira-importer

Description

@jira-importer

Slawomir Jaranowski opened MASSEMBLY-1022 and commented

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.


Affects: 3.7.0

Issue Links:

  • 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
    ("fixes")
  • MASSEMBLY-1008 Assembly plugin handles scopes wrongly
    ("is caused by")

Remote Links:

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions