Result for 942C3D5B0620DDDA394B89B4AB27840040BDA3AB

Query result

Key Value
FileName./usr/share/maven-metadata/munge-maven-plugin.xml
FileSize1882
MD57EE2A655C458A4E00B5A7BB1D70D4CE3
SHA-1942C3D5B0620DDDA394B89B4AB27840040BDA3AB
SHA-256E64448E0F0B96240717E0CBC8210E0B343E44CCB1745D352A7F82504D4857AD2
SSDEEP48:cmAWUxsRbtKubrCtGtKbSIAkSxSSAgxS7hasRbtKubskCaGtKbSIAkSxSSAgxS7E:LAtx84MCtG4bSIRUXXca84ACaG4bSIRO
TLSHT1DD414BE498FD5471617D1BD0CA7795F15FC8916BB4015088F0CC21CA8F9ACCA42B3532
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
MD5FE10F1EC5D6D242C74F328E77287672A
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
PackageRelease1.2
PackageVersion1.0
SHA-12A3052AA7FAEBE0802D00DDE4D3DC457881A1541
SHA-25660277E0FB096C10D7A05E7C1B612EF0511ECD639826C7F0542F139F982CC1EC4