Download JAR files tagged by changed with all dependencies

TimoCloud is a Minecraft server/proxy management system ("Cloud System"). It will care about keeping online enough servers/proxies of every kind. But it's more than that. Thank to its algorithms, you'll never have to care again about servers or resources. TimoCloud automatically chooses servers with low CPU usage and enough available RAM to start your instances. And its integrated Flow-System makes updating templates easier than ever before: Edit one file in a server template, and the update will automatically be deployed to all bases (a.k.a. "Wrapper"). But of course, only the changed files will get updated.

Bundle with a synchronous activator which will install OGEMA resources from XML (.ogx) or JSON (.ogj) files located in config/resources (default). This requires a running OGEMA framework when the bundle is started and enables the installation of basic resources before other applications are activated. Also adds a service for felix fileinstall that will install such resource files. Files installed through fileinstall will be reinstalled when they are updated or when a newer version of an installed file is found after a restart (using the file's last modification timestamp). Files installed from the configuration directory will only be reinstalled on a restart, if they have been changed.

This module allows you to enable suppressions for turning off warnings about Restricted APIs. !!!WARNING!!! Classes are marked as @Restricted for a reason and this module should not be used lightly! It implies that the author does not intend for them to be used outside their defined scope and as such they may be changed/modified/removed at any stage without warning. A simple upgrade of the dependency may break your module. Use at your own risk. You should try to not use @Restricted classes in the first place, but if you _must_ use them, this is a less-brutal approach than just disabling the access-modifier-checker entirely

Bond is a small library that can be used to spy values and mock functions during tests. Spying is a replacement for writing the assertEquals in your test, which are tedious to write and even more tedious to update whem your test setup or code inevitably changes. With Bond, you separate what is being verified, e.g., the variable named output, from what value it should have. This way you can quickly spy several variables, even have structured values such as lists or dictionaries, and these values are saved into an observation log that is saved for future reference. If the test observations are different you have the option to interact with a console or visual tool to see what has changed, and whether the reference set of observations need to be updated.

Welcome to the Blazegraph/TinkerPop3 project. The TP3 implementation has some significant differences from the TP2 version. The data model has been changed to use RDF*, an RDF reification framework described here: https://wiki.blazegraph.com/wiki/index.php/Reification_Done_Right. The concept behind blazegraph-gremlin is that property graph (PG) data can be loaded and accessed via the TinkerPop3 API, but underneath the hood the data will be stored as RDF using the PG data model described in this document. Once PG data has been loaded you can interact with it just like you would interact with ordinary RDF - you can run SPARQL queries or interact with the data via the SAIL API. It just works. The PG data model is also customizable via a round-tripping interface called the BlazeValueFactory, also described in detail in this document.

JmDNS is a Java implementation of multi-cast DNS and can be used for service registration and discovery in local area networks. JmDNS is fully compatible with Apple's Bonjour. The project was originally started in December 2002 by Arthur van Hoff at Strangeberry. In November 2003 the project was moved to SourceForge, and the name was changed from JRendezvous to JmDNS for legal reasons. Many thanks to Stuart Cheshire for help and moral support.

Dyndns JMCE is an application deployed to a JMCE server whose purpose is to login to a Dyndns account because if that's not done on a regular basis the account gets deleted. MAVEN: mvn [-DskipTests] clean site package NOTES: After unzipping the binary on the JMCE server, make sure to copy the ferris-dyndns-jmce-private-0.0.1.jar to /bin so the app has the username/passwords it needs. 0.0.2: Changed project name from ferris-jmce-dyndns to ferris-dyndns-jmce Removed java.util.logging.Logger for Log4j Split into muli-module project 0.0.3: Update screen scrape based on changes to the dyndns website. 0.0.4: Update screen scrape (again) based on changes to the dyndns website. Changed parent to "ferris-standard-project" 0.0.5: - Update screen scrape (again) based on changes to the dyndns website. - Update pom.xml configuration to be in line with new parent pom. - Update project site

JmDNS is a Java implementation of multi-cast DNS and can be used for service registration and discovery in local area networks. JmDNS is fully compatible with Apple's Bonjour. The project was originally started in December 2002 by Arthur van Hoff at Strangeberry. In November 2003 the project was moved to SourceForge, and the name was changed from JRendezvous to JmDNS for legal reasons. Many thanks to Stuart Cheshire for help and moral support.

Avalon Excalibur's resource management code allows you to be notified when a resource has changed. There are two methods of resource management: active and passive. Passive resource management acts as a holder for resources, and after the resource has been modified through it's normal API, notification goes to all listeners. Active resource management does the same, but it also polls the resources periodically to see if the resource was modified through an external method. Active resource management is perfect for monitoring files because they can be modified by external programs, and your program will be notified when the change occurs instead of constantly polling it.