Result for 869E97E40D0B451798C6486223851634C85157AB

Query result

Key Value
FileName./usr/share/maven-metadata/munge-maven-plugin.xml
FileSize1882
MD5D7D9022AC2806E0329D7732F302890AA
SHA-1869E97E40D0B451798C6486223851634C85157AB
SHA-25658AAD5D7BD1E8FD4641371BB43A94EF9AC89FB3B70C9CB5C1D9D051AFF1367F0
SSDEEP48:cmAdsRbtKubrC/BGtKbSIAkSxSSAgxS7hasRbtKubskC1GtKbSIAkSxSSAgxS7hW:LAd84MCpG4bSIRUXXca84AC1G4bSIRUf
TLSHT1A74137E599FDA07062BD1BC0CA7799F15FC8916BB4025488F0CC218A8F8ECCB42B3532
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
MD5F616BE802601DCC27BC59818C0ED9C31
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.456
PackageVersion1.0
SHA-1317D77C01B5412A415586E471B9ADAE3FB42CB00
SHA-256C7AAFF14009D194E964A5798F36B2A0EA83B14CDEC5D4929E63158C65F2D42F4