Result for C1C482AE0379ECAB40049FAFC1ECBD466084EE42

Query result

Key Value
FileName./usr/share/maven-metadata/munge-maven-plugin.xml
FileSize1882
MD576B166C72D8D68B17337EF72F290C033
SHA-1C1C482AE0379ECAB40049FAFC1ECBD466084EE42
SHA-2564224A10C4937A47D463C66D216A84A0609403DAB58911D99FB248C248CD90008
SSDEEP48:cmA5sRbtKubrCLGtKbSIAkSxSSAgxS7hasRbtKubskCeB5GtKbSIAkSxSSAgxS7E:LA584MCLG4bSIRUXXca84ACePG4bSIRO
TLSHT165414BD598FD9470627D1BC0DA779AF55FD8916BB4029088F0CC21CA8F8ACCB42A3132
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
MD5D08F36C78A716161C859A1581696A524
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.719
PackageVersion1.0
SHA-10593581D90C53819D0F46CD4F093E79401161A3D
SHA-25600C6BFAEC414479FB2C5ACBB9C8DF5182B212BF707FE3E562FA345FC4A1F2DF3