Key | Value |
---|---|
FileName | ./usr/share/maven-poms/munge-maven-plugin/munge-maven-plugin.pom |
FileSize | 2867 |
MD5 | 9D53264271AE7C3E4319242848DADB42 |
SHA-1 | 44661878B4A100672FD2C334FC760898D963B421 |
SHA-256 | 17E28D5AC0DCDB1EBF8DA9EA97B7751350B408ED0261D1DE7640E3104A1B80EF |
SSDEEP | 48:c9p8FHUshc95tKIJsxbtKub1Ynjn7SFgKnvQzgD9d4QkSmCQgmCxfDKBmwKubwNR:PHUrL4ss4+m772gRzg9d4BuZAypAm+cD |
TLSH | T1DD516FB194FD84B222A90BC1DAB698D56FFCC1AFA082C088F4DC6555AF7DCC94263912 |
hashlookup:parent-total | 35 |
hashlookup:trust | 100 |
The searched file hash is included in 35 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | D08F36C78A716161C859A1581696A524 |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 7.719 |
PackageVersion | 1.0 |
SHA-1 | 0593581D90C53819D0F46CD4F093E79401161A3D |
SHA-256 | 00C6BFAEC414479FB2C5ACBB9C8DF5182B212BF707FE3E562FA345FC4A1F2DF3 |
Key | Value |
---|---|
MD5 | 9814D5917027912F1C640260B934623A |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageMaintainer | Fedora Project |
PackageName | munge-maven-plugin |
PackageRelease | 1.fc20 |
PackageVersion | 1.0 |
SHA-1 | 07DC7E41FE9E5916B3C60DDD1891C9E395D4258A |
SHA-256 | 02EFD16F4F63860387C81084F31C794E203D04F0393FB1E25FA3EAAF6C0C245F |
Key | Value |
---|---|
MD5 | 1A6A88C0FF8F9C897AB5244F852808C4 |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageMaintainer | Fedora Project |
PackageName | munge-maven-plugin |
PackageRelease | 4.fc21 |
PackageVersion | 1.0 |
SHA-1 | 1F06433D17D14E248479D37A5731EE3D2E9C35D4 |
SHA-256 | 4330936DC3693AF5240CBDDFFA0CDA22FD70E0F2CE2405B9DFD13C6BE5B78E40 |
Key | Value |
---|---|
MD5 | 92B6AA0E8D51FF18F22BF1CCAC5DAF2C |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 7.545 |
PackageVersion | 1.0 |
SHA-1 | 1FE9FBD84E3A1320148578AD5570FBCCA4ECEE22 |
SHA-256 | CA4443F0D21F41F0C495A0314E1DB16DFCDC3D877C8F275EA98DFCBC10DC1ED2 |
Key | Value |
---|---|
MD5 | 1968CC6A527B58899034F99357C77BBC |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 150400.7.30 |
PackageVersion | 1.0 |
SHA-1 | 298A5A0A95153794C439D4D773E492A3C4760A03 |
SHA-256 | E8A6D9A2F51AC777BA8DA271BE65700F06D016D72955B4B85871983A337569A9 |
Key | Value |
---|---|
MD5 | FE10F1EC5D6D242C74F328E77287672A |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 1.2 |
PackageVersion | 1.0 |
SHA-1 | 2A3052AA7FAEBE0802D00DDE4D3DC457881A1541 |
SHA-256 | 60277E0FB096C10D7A05E7C1B612EF0511ECD639826C7F0542F139F982CC1EC4 |
Key | Value |
---|---|
CRC32 | 43F68F5F |
FileName | munge-maven-plugin-1.0-2.el7.noarch.rpm |
FileSize | 26308 |
MD5 | DC8DBED2BF5E13B4449C878B7B8CA539 |
OpSystemCode | 362 |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageMaintainer | CentOS BuildSystem <http://bugs.centos.org> |
PackageName | munge-maven-plugin |
PackageRelease | 2.el7 |
PackageVersion | 1.0 |
ProductCode | 202232 |
SHA-1 | 2C0BB801F94C09D25639E6E595EF576AC1DCAA7A |
SHA-256 | D29CF6BE397E0B9CFE3D152C5B98FA1B7E0A37E84433C65CB249975BA589620B |
SpecialCode | |
db | nsrl_modern_rds |
insert-timestamp | 1646994833.9661546 |
source | NSRL |
Key | Value |
---|---|
MD5 | 1AEFE58E1638390FC4390E093EF47DCB |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 7.298 |
PackageVersion | 1.0 |
SHA-1 | 2CFCF5EAAE87689926F7559E553260CA41857620 |
SHA-256 | 2638D1D8484685AF30CC4CB9608B829376F891AE2714FAECD678ACF31581561C |
Key | Value |
---|---|
MD5 | F616BE802601DCC27BC59818C0ED9C31 |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageName | munge-maven-plugin |
PackageRelease | 7.456 |
PackageVersion | 1.0 |
SHA-1 | 317D77C01B5412A415586E471B9ADAE3FB42CB00 |
SHA-256 | C7AAFF14009D194E964A5798F36B2A0EA83B14CDEC5D4929E63158C65F2D42F4 |
Key | Value |
---|---|
MD5 | 9840F4A1F00104B766235B821F8EB691 |
PackageArch | noarch |
PackageDescription | Munge 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. |
PackageMaintainer | CBS <cbs@centos.org> |
PackageName | rh-maven33-munge-maven-plugin |
PackageRelease | 2.12.el7 |
PackageVersion | 1.0 |
SHA-1 | 3E5176C72F7AEC060D3A2BFC81611BF0F7F0AF61 |
SHA-256 | 79287290058B4C01CE454827F29FDB704D935A33D342AFCFAF49806225B7B6A2 |