Download JAR files tagged by back with all dependencies

Use the Branch SDK (branch.io) to create and power the links that point back to your apps for all of these things and more. Branch makes it incredibly simple to create powerful deep links that can pass data across app install and open while handling all edge cases (using on desktop vs. mobile vs. already having the app installed, etc). Best of all, it is really simple to start using the links for your own app: only 2 lines of code to register the deep link router and one more line of code to create the links with custom data.

This project provides the best of maven easily consumable a maven parent project, called MavenParent. With this project you get: Checkstyle and PMD checks that will work by default in eclipse with m2e-code-quality. OWASP vulnerability checks of your dependencies. Easy application of BSD-3 clause license to all your code with mycila-license plugin. The ability to easily enforce semantic version on a jar project with japicmp. Prevent duplicates on your classpath with basepom's duplicate-finder. All of the above can be configured or disabled easily with properties, just check their docs, except takari. A whole slew of pretty maven reports including the above are generated in the maven site. The ability to easily deploy to oss nexus, and publish maven generated sites back to github's sites pages.

Smart Commit JDBC Driver enables 'smartcommit' mode for all JDBC drivers. In Smart Commit mode a JDBC connection will execute all queries in autocommit mode until it encounters a write operations. From the first write operation until the following commit or rollback, the connection will operate in transactional mode. It will then switch back to autocommit and remain in autocommit until it once again encounters a write operation. Using a JDBC connection in Smart Commit mode will reduce the number of read locks needed. Operating a JDBC connection in Smart Commit mode effectively reduces the isolation level of a transaction to READ_COMMITTED for all queries that are executed *BEFORE* a write operation in a transaction. All queries that are executed *AFTER* a write operation in a transaction, will be executed using the configured isolation level of the JDBC connection.

<p> MMBase Utils is a part of MMBase, but can also be used in other projects. It contains several kind of utility classes.</p> <p>Highlights:</p> <ul> <li>An implementation of 'events'. Threads can use this to communicate certain things. Using mmbase-clustering, these events can also be sent to other servers.</li> <li>A logging framework</li> <li>A framework for string and byte array transformeration, plus a whole lot of implemetentations for that.</li> <li>Several java.util like classes (collections, dateparsing)</li> <li>File type recognition ('magicfile')</li> <li>The MMBase resourceloader, a generic fall-back mechanism for configuration files and similar resources.</li> <li>...</li> </ul>

This is a plugin to Madura Objects. It provides a rules/constraint engine to assist with validation, deriving new values from user inputs (eg total of invoices entered on this customer) an manipulating metadata (eg because the amount is above X we make some field readonly). Note that the Java that is using the monitored objects is quite unaware of the rules layer implemented here. That means you can change rules without having to go back to your Java code, and it also means you don't have to wonder if everything implemented the same rules. Anything using that Java object has the rules (unless you turn them all off).

The rooster crows immediately before sunrise, the rooster causes the sun to rise. Using GraphX to detect possible causes and effects between time related events. We observe a true causation signal by generating random correlations over same events at different time and back propagate these scores to their most connected events. Finally, we extract the most probable causes and effects together with a score of aggressiveness (how likely an event could explain downstream effects) and sensitivity (how likely an event results from an upstream cause).

The ServiceMix Drools component provides JBI integration to the Drools Rules Engine. It can be used to deploy a rules set that will implement a router or an actual service. A router will mostly act as a transparent proxy between the consumer and the target service provider mad will mostly be implemented by the jbi.route(uri) method below. This method creates a new exchange identical to the one received by the component and will send it to the specified destination. You can also send back a Fault if needed. A router can also be implemented by using directly the JBI Apis (available with the jbi helper) by using the provided client.

This project creates a bundle of the Impex legacy tool that is decoupled from Subversion. It creates a jar file that has the exact same binaries, source, directory structure, and layout as the Impex contained inside Subversion. Since it is published as a versioned jar file, it can be referenced in other processes (like the Rice binary release process) without those processes needing the ability to connect back to Subversion to check out the tool. Processes that need access to the legacy Impex tool can thus express a normal maven dependency in order to obtain it.

The purpose of this project is to provide a Java API and implementation capable of reading the data files of a Creative Memories http://www.creativememories.com/) Memory Manager (http://www.creativememories.com/MainMenu/Our-products-and-services/Digital-Scrapbooking/Memory-Manager%e2%84%a2) Memory Vault mvn site package 0.0.1 -Initial Release supporting Memory Manager 3 0.0.2 -RC1 * Refactor of 0.0.1 to support on-demand construction of the data tree instead of building the entire tree up front. * Change pom parent to ferris-standard-project -RC2 * Added Observable back to Manifest. * Updated DAO to accept an Observer.

All Roads Lead to ROME. ROME is a set of Atom/RSS Java utilities that make it easy to work in Java with most syndication formats. Today it accepts all flavors of RSS (0.90, 0.91, 0.92, 0.93, 0.94, 1.0 and 2.0), Atom 0.3 and Atom 1.0 feeds. Rome includes a set of parsers and generators for the various flavors of feeds, as well as converters to convert from one format to another. The parsers can give you back Java objects that are either specific for the format you want to work with, or a generic normalized SyndFeed object that lets you work on with the data without bothering about the underlying format.