Result for 21B9E1CC4B22ED8092CF8FD62C90CA9CC71620C6

Query result

Key Value
FileName./usr/share/maven-metadata/munge-maven-plugin.xml
FileSize1882
MD55AE73C511FB879B98749E8A6E702425C
SHA-121B9E1CC4B22ED8092CF8FD62C90CA9CC71620C6
SHA-25685CF7A4DD5E25321C9AFC25DB0C82ABFDF900B67ABBBE0C13A27B4A9656C2B3A
SSDEEP48:cmAWsRbtKubrCpaGtKbSIAkSxSSAgxS7hasRbtKubskCGIGtKbSIAkSxSSAgxS7E:LAW84MCwG4bSIRUXXca84ACGIG4bSIRO
TLSHT18D4139E598FD9471617D1BC0CA779AF55FC8D16BA4029488F4CC218A8F9ACCA42B3532
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD592B6AA0E8D51FF18F22BF1CCAC5DAF2C
PackageArchnoarch
PackageDescriptionMunge is a purposely-simple Java preprocessor. It only supports conditional inclusion of source based on defined strings of the form "if[tag]", "if_not[tag]", "else[tag]", and "end[tag]". Unlike traditional preprocessors, comments, and formatting are all preserved for the included lines. This is on purpose, as the output of Munge will be distributed as human-readable source code. To avoid creating a separate Java dialect, the conditional tags are contained in Java comments. This allows one build to compile the source files without pre-processing, to facilitate faster incremental development. Other builds from the same source have their code contained within that comment. The format of the tags is a little verbose, so that the tags won't accidentally be used by other comment readers such as javadoc. Munge tags must be in C-style comments; C++-style comments may be used to comment code within a comment. Like any preprocessor, developers must be careful not to abuse its capabilities so that their code becomes unreadable. Please use it as little as possible.
PackageNamemunge-maven-plugin
PackageRelease7.545
PackageVersion1.0
SHA-11FE9FBD84E3A1320148578AD5570FBCCA4ECEE22
SHA-256CA4443F0D21F41F0C495A0314E1DB16DFCDC3D877C8F275EA98DFCBC10DC1ED2