Key | Value |
---|---|
FileName | ./usr/share/doc/libmunge-maven-plugin-java/README |
FileSize | 1072 |
MD5 | 8B7C739EEFDA96E62FDC5F449850D61B |
SHA-1 | 6935392524C3EDB987CE42F13945F376C656976A |
SHA-256 | D15913107A6C37C71FC4077098440444EB08690F80BC3A849590A51DE83EEE32 |
SSDEEP | 24:ZDGb6oW3ytqXueUWdxo14h2JwBTA3QgpgEMOAhFJpT10RcGJmal:ZDGbvW37UyhrzEA3JpTKdDl |
TLSH | T1EC11F037BACC3175091022D15A4463DA7F68BA146B70017FA429C15CA7DB9E79413FAD |
hashlookup:parent-total | 46 |
hashlookup:trust | 100 |
The searched file hash is included in 46 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 4F4A0B6466121AEEDBE78D05D1CA056D |
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 | 16.fc32 |
PackageVersion | 1.0 |
SHA-1 | 041DB895802360C4FA0F996D1935D4D543F5490C |
SHA-256 | 954FC533C4C701F6F5E4709CF26AB2337C89CAB4456606B526A8402A0FD74434 |
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 |
---|---|
FileSize | 32270 |
MD5 | 49410CC0962BB1A2106D11793E7C2C95 |
PackageDescription | Maven plugin to pre-process Java code - documentation The Munge Plugin for Maven provides mojos to munge (pre-process) Java code. . It only supports conditional inclusion of source based on defined strings of the form "if[tag]", "if_not[tag]", "else[tag], and "end[tag]". . This package contains the API documentation of libmunge-maven-plugin-java. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | libmunge-maven-plugin-java-doc |
PackageSection | doc |
PackageVersion | 1.0-1 |
SHA-1 | 2416C5DDE954E63A28B9DE3F6DC3C3E799EA2E87 |
SHA-256 | 2C73CFC15BE0082765841CE0BAAF1EE49D4535603B606633F7DAA3BC08A91DD8 |
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 |