Download JAR files tagged by move with all dependencies

Module that contains dependencies to all modules normally needed for a basic Cocoon webapp. Cocoon blocks should normally depend on this modules, as the exact content of the more fine grained sitemap, pipeline and support modules is not stable yet. This module also contains some classes, configuration files and tests that we not have decided where to move yet.

A light weight and high performance Java caching library. Android and Java 6 compatible. This artifact contains the implementation of the core functionality of cache2k. For using and integrating cache2k in applications please use the definitions in the cache2k-api artifact only. Classes within the implementation code are not stable within releases and may move or even disappear.

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 Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module. Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars. Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the subsystem-templates by wildfly-server-provisioning-maven-plugin. Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.

EnOS Device And Asset API pojo 0.2.14-SNAPSHOT ota api pojo and event 0.2.20-SNAPSHOT The Response objects returned by GetEvent and SearchEvent queries are added (including: outputData, eventName, outputNames fields) 0.2.21-SNAPSHOT Increase the internationalization of the four-element description field of the model 0.2.22-SNAPSHOT add some pojo class for private api 0.2.23-SNAPSHOT model-service open api的接口中thingModel增加category模型类型字段 0.2.24-SNAPSHOT 部分search接口增加realTime字段 0.2.25-SNAPSHOT firmware add tag function 0.2.27-SNAPSHOT add max and min fields 0.2.28-SNAPSHOT asset tree api for amc/city infra 0.2.29-SNAPSHOT fix thingModel enableMeasurepointValidate 0.2.30-SNAPSHOT enhancement of search model and update asset and alert engine 增加告警规则sdk 0.2.31-SNAPSHOT move asset node 2.4.0-SNAPSHOT upgrade to 2.4 for support DCM 2.4GA 2.4.1-SNAPSHOT service parameter supports "Required" and "Default Value" fields 2.4.2-SNAPSHOT upgrade to 2.4 for support DCM 2.4GA jar 升级 2.4.3-SNAPSHOT add alert-engine v2.5 alertRule openAPI

In C++, writing a loop that iterates over a sequence is tedious. We can either use iterators, which requires a considerable amount of boiler-plate, or we can use the std::for_each() algorithm and move our loop body into a predicate, which requires no less boiler-plate and forces us to move our logic far from where it will be used. In contrast, some other languages, like Perl, provide a dedicated "foreach" construct that automates this process. BOOST_FOREACH is just such a construct for C++. It iterates over sequences for us, freeing us from having to deal directly with iterators or write predicates.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Lightbend subscription does not cover support for these modules.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Lightbend subscription does not cover support for these modules.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Lightbend subscription does not cover support for these modules.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Lightbend subscription does not cover support for these modules.