Download JAR files tagged by provide with all dependencies

ADIF Processor visualizes contacts in your input file on Google Earth. It generates a Google Earth Project file, also known as a KML file, with a visualization of each contact in the ADIF/SOTA CSV input file where station locations can be determined. It parses structured tags in comments to enrich the correct ADIF output file. QRZ.com is used to determine station locations and provide additional information in the ADIF output file. The markdown/text file output contains a listing of contacts. The processor contains activity databases for the main outdoor activities such as SOTA, POTA, GMA, HEMA etc.

The standardization of KHQR code specifications will help promote wider use of mobile retail payments in Cambodia and provide consistent user experience for merchants and consumers. It can enable interoperability in the payment industry. A common QR code would facilitate payments among different schemes, e-wallets and banks and would encourage small merchants to adopt KHQR code as payment method. KHQR is created for retail or remittance in Cambodia and Cross-Border. It only requires a single QR for receiving transactions from any payment provider through Bakong including Bakong App.

Essentials is a set of Java version 17 (and later) building blocks built from the ground up to have no dependencies on other libraries, unless explicitly mentioned. The Essentials philosophy is to provide high level building blocks and coding constructs that allows for concise and strongly typed code, which doesn't depend on other libraries or frameworks, but instead allows easy integrations with many of the most popular libraries and frameworks such as Jackson, Spring Boot, Spring Data, JPA, etc.

Dryuf BigIo is stateless, unlimited IO framework, solving few design problems of original JDK. It mainly provides three things - FlatBuffer with 64-bit address space and being stateless. Additionally, it provides FlatChannel interface and few implementations - providing the arbitrary reads and writes from chosen position. This is implemented only in FileChannel in NIO so this interface makes it easier to provide those stateless reads and writes on virtual channels too. BigIo also provides committable objects, allowing marking the object as completed or incomplete, so it correctly results into success or exception on receiving side.

This API determines the holidays for a given year, country/name and eventually state/region. The holiday data is stored in XML files (one for each country) and will be read from the classpath. You can provide your own holiday calendar XML file or use any of the provided ones. Currently, there are over 70 countries supported like the following: * United States * Germany * France * India * Australia * and so on Besides, those there will be more special calendars like currently existing NYSE calendar (New York Stock Exchange).

The Config project is home to Sakai configuration and localization files. Config includes several versions of sakai.properties, a text file containing a series of key/value pairs that provide a convenient mechanism for defining a variety of configuration options for Sakai tools, services, supporting database and UI-related text such as copyright statement, institutional name, server name, etc. Settings in sakai.properties are read on startup; thus changes to sakai.properties only take effect after you restart Sakai's servlet container (typically Apache Tomcat).

The JAX-SB Generator is a comprehensive framework to facilitate the use of XML in software languages such as Java. This framework intends to provide tools that will allow a developer to easily integrate XML interoperability, bind XML Schemas, and analyze XML Schemas for use with any software. Currently there is only one language and one application that is supported: XML Binding in Java. Next on the agenda is the development of analysis tools for XML Schema Documents. For instance, imagine a tool that will allow you to determine whether an XSD complies to best-practices. This tool will: 1) produce warnings for structures that do not comply to best-practices, 2) tell the developer whether the logical structure can be transformed linearly to a form that complies to best-practices, and 3) to automatically produce an XSD that maintains the logical structure of the original document but now fully complies to best-practices. This is just one of many tools that will be available shortly. In the meantime, check out the binding application.