Download JAR files tagged by recommended with all dependencies

We skip staging of some submodules, but if you skip staging in the last submodule it skips all staging (a serious error in the design of the nexus staging plugin that has been closed "wontfix" - issues.sonatype.org/browse/NEXUS-9138). The backup solution to that problem is to skip the deploy phase in the submodule. We want to deploy the artifact of bedrock-site to AWS, but not publish the war file to nexus. The recommended solution is to add this dummy node at the end of the submodule list.

Extensions built on Microsoft Azure Event Hubs${line.separator} This library has been replaced by new Azure SDKs, you can read about them at https://aka.ms/azsdkvalueprop. The latest libraries to interact with the Azure Event Hubs service are:${line.separator} 1. https://search.maven.org/artifact/com.azure/azure-messaging-eventhubs${line.separator} 2. https://search.maven.org/artifact/com.azure/azure-messaging-eventhubs-checkpointstore-blob${line.separator} It is recommended that you move to the new package.

This project contains a logback.xml which sets up logging for brooklyn, using files supplied in the upstream brooklyn-logback-includes project. - One recommended way to configure logging on a project is to add this as an *optional* *runtime* dependency in a project's pom.xml file, so that logback.xml is on the classpath when that project is run but it is *not* exported to new/dependent projects thus allowing them to supply their own logging. - For more information see the logback.xml file in this project or the Logging section of the web site / user guide.

This composite contains a restricted version of easyb-core, so that people can depend on named releases of easyb without having to keep a version range of easyb-core if they so wish. It provides compatibility with existing uses of easyb, and easyb versioning (0.9x). It is *recommended* that people stop using this artefact and instead use the easyb-core with a version range of [1,2] so updated bug fixes and feature releases flow in.

Includes 2 main parts: - Path finding through 2D polygons using the A star algorithm and navigation-mesh generation Field of vision / shadows / line of sight / lighting. The basic polygon and point classes are the KPolygon and KPoint. KPolygon contains a list of KPoints for vertices as well as a center (centroid), area, and radius (circular bound or distance from center to furthest point). KPolygon was born out of the need for a more game-oriented and flexible polygon class than the Path2D class in the standard Java library. KPolygon implements java.awt.geom.Shape so it can be easily drawn and filled by Java2D's Graphics2D object. - This API provides path-finding and field-of-vision. For other complex geometric operations such as buffering (fattening and shrinking) and constructive area geometry (intersections and unions) it is recommended to use the excellent Java Topology Suite (JTS). The standard Java2D library also provides the Area class which can be used for some constructive area geometry operations. Note that there is a utility class PolygonConverter that can quickly convert KPolygons to JTS polygons and vice versa.

This project aims to offer an easy-to-extend Java DAS server framework. It offers several advantages: * Implementing data sources is very easy but also flexible and powerful. * Data caching is built into the system, with access to the caching mechanism made available to the data sources. * All aspects of the server are highly configurable, including selecting options where the DAS 1.53 specification offers choices to the implementor. * The latest Java technologies have been used throughout the system to optimise performance and simplify data source development. * Wherever possible the same terminology is used in the API as in the DAS specification and XML - again, making data source development more easy. * The server allows XSLT transforms of the DAS XML to be configured to provide a simple DAS client view (limited to the single DAS source). More details of the DAS protocol, DAS servers and DAS clients can be found at http://www.biodas.org/wiki/Main_Page. The first version of this server is a complete implementation of Distributed Sequence Annotation System (DAS) Version 1.53. If you are interested in learning more about DAS 1.53, the specification is highly recommended as a concise and complete description of the DAS protocol that can be obtained from: http://biodas.org/documents/spec.html