JSON output: MAN-1 and MAN-4 entryPath parameter

[maria-messerschmidt]

The message for MAN-1 and MAN-4 both use a parameter with name: entryPath.

{
"message" : {
"id" : "MAN-1",
"severity" : "ERROR",
"message" : "The manifest SHALL contain an entry for every file in the package, zip entry extra.xml has no corresponding manifest file entry.",
"parameters" : [ {
"name" : "entryPath",
"value" : "extra.xml"
} ],
"timestamp" : "2025-03-21 07:48 UTC",
"sub_message" : ""
},
"path" : "extra.xml"
}

{
"message" : {
"id" : "MAN-4",
"severity" : "ERROR",
"message" : "The manifest SHALL contain an entry for every file in the package, manifest file entry Thumbnails/thumbnail.png has no corresponding zip entry.",
"parameters" : [ {
"name" : "entryPath",
"value" : "Thumbnails/thumbnail.png"
} ],
"timestamp" : "2025-03-21 07:48 UTC",
"sub_message" : ""
},
"path" : "META-INF/manifest.xml"
}

For MAN-1, this makes sense since it refers to the zip entry in the same way it does for the rest of the messages but in MAN-4, it is a manifest entry that doesn't have a zip entry. Since it is the only parameter for both, it is not a big deal, but it should be documented that the parameter entryPath can refer to different things.