Key | Value |
---|---|
FileName | ./usr/share/maven-poms/JPP.logback-logback-classic.pom |
FileSize | 12959 |
MD5 | 83D53624261BCA7251572CD0009F27AC |
SHA-1 | 034395B929B0368EDBBEE726C80F3CCB8F3E4109 |
SHA-256 | 1BE01457CB3025D7F6EBAB71E3CB8305BAB6538118699539ED27D0DEBFDF8BAE |
SSDEEP | 384:wufelxkr/fkStZJp2OBe+p4nRwwvWlap/aQA1oWj9grjqI39ebe8NLcO:wAelxkr/fkStZJp2OBe+p4RwwvWlap/m |
TLSH | T1F642BB78D8CEA07161B64DC5CEB1C575FF2A8167D00A9048F58CA3872FBCDCA847795A |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 3ED86A9831031FE973A31B831164ADC5 |
PackageArch | noarch |
PackageDescription | Logback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core. |
PackageMaintainer | Fedora Project |
PackageName | logback |
PackageRelease | 3.fc18 |
PackageVersion | 1.0.6 |
SHA-1 | 311FAE0FC234FA653DFC6FC125D2B62C8033B19A |
SHA-256 | D543A9B54673A41FCACFC6FC10484E4EEDAE482043D5EC645BD889CDF41F991F |
Key | Value |
---|---|
MD5 | 952E36C8C93A9A5E0F349BFA1C6AECA8 |
PackageArch | noarch |
PackageDescription | Logback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core. |
PackageMaintainer | Fedora Project |
PackageName | logback |
PackageRelease | 3.fc18 |
PackageVersion | 1.0.6 |
SHA-1 | CB403DEC4B7F952C8ADC6C0EC0EEEEC3850ED26B |
SHA-256 | 5245468524C7F062B137B1379BC53762399F0E8F2500339D3954B65F4626F065 |
Key | Value |
---|---|
MD5 | B99A1E3C3CC0C11FC041DD4A323F1941 |
PackageArch | noarch |
PackageDescription | Logback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core. |
PackageMaintainer | Fedora Project |
PackageName | logback |
PackageRelease | 3.fc18 |
PackageVersion | 1.0.6 |
SHA-1 | 3E893BABFE31EF2A0D2CC70E684B8C279AEECE6D |
SHA-256 | 19088F83482AEED3B02DAB7E7C356EB97778B169A3654D2E6E5CD48E4132900C |