Parents (Total: 3)

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
FileSize	2080028
MD5	6F7F9E311289DB5EE67EADCD60C2B85D
PackageDescription	Apache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainer	Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
PackageName	liblog4j2-java
PackageSection	java
PackageVersion	2.17.0-1~deb11u1
SHA-1	2FE8079A450386E0F7BA306A21225A542D650113
SHA-256	BC3B525AC61CBEF2A4CE7CB83B1337F0BA6D2FBCA1AC18A378700DCB92AAB17B

Key	Value
FileSize	2080200
MD5	68E09F47EFD064E0D21CD52BB51A04D5
PackageDescription	Apache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainer	Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
PackageName	liblog4j2-java
PackageSection	java
PackageVersion	2.17.0-1
SHA-1	14FB53E20A27AAA1301F88D314C2AFC09D8E8754
SHA-256	AE785BF30505F6DC7C2D7D60C3BDDC85A4D9462E99FE2BDA142EE0AFE0678326

Key	Value
FileSize	2079820
MD5	17AF905049F78235CCE0BEE30D801B38
PackageDescription	Apache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainer	Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
PackageName	liblog4j2-java
PackageSection	java
PackageVersion	2.17.0-1~deb10u1
SHA-1	567114F46336F639C26569F7757ECD2DD1DDCE39
SHA-256	03EA31D232051FD1CC9D73D1A21BF01C261F3D03F8364D57BC2F36DCE48DF46C