home:fstrba:maven:test

https://download.opensuse.org/repositories/home:/fstrba:/maven:/test/openSUSE_Factory/ Java:Factory

Devel project of Java packages for openSUSE:Factory

The packages here are used for publishing to openSUSE:Factory. They are also used for curious user to test latest and greatest features available in the OpenJDK world. https://download.opensuse.org/repositories/Java:/Factory/openSUSE_Factory/ openSUSE:Factory:LegacyX86

openSUSE Factory Port for i586 (32bit)

This is a project clone to build the entire openSUSE:Factory for i586 (32bit) https://download.opensuse.org/repositories/openSUSE:/Factory:/LegacyX86/standard/ openSUSE:Factory

The next openSUSE distribution

openSUSE Tumbleweed: The Bleeding Edge, Perfected. Tumbleweed is the ultimate rolling release distribution, providing the latest software as it’s released, built upon a foundation of world-class stability and testing. * Always Current: Get the newest kernel, IDEs, desktops, and applications automatically. * Powerfully Stable: Experience the velocity of a rolling release without sacrificing the reliability you depend on. * Engineered for Professionals: The top choice for Developers, Power Users, and openSUSE Contributors who need the best tools for the job. If you demand the latest stable software, your choice is Tumbleweed. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/tumbleweed/repo/oss/ httpcomponents-core

Set of low level Java HTTP transport components for HTTP services

HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.