Download JAR files tagged by packaged with all dependencies

Ferris SLiSE (Spectral Line Search Engine) Common contains code which is common to the different ways SLiSE is packaged and distributed. Because of the way Maven works, it's easier to create seperate projects to package and distribute SLiSE as either an Applet Application, a Desktop Application, or a Java Web Start Application mvn clean site package 0.0.1 Convert from Oak to Ferris

mime-util is a simple to use, small, light weight and fast open source java utility library that can detect the mime types of files and streams. Due to the use of regular expressions and the java.nio packages it requires at least Java 1.4. mime-util uses file extension mappings and the magic.mime rules files located on your system as used by the Unix file(1) command. For OS's that do not support the Unix file(1) command, such as Windows, the library comes pre-packaged with a generic magic.mime file.

Dhelm is a set of java-based open source libraries which can be used to develop software to perform technical analysis in stock market. The dhelm-indicator package includes APIs to calculate few common indicators. APIs for following indicators have been packaged into the v 1.0.0- 1. Simple Moving Average(SMA). 2. Exponential Moving Average(EMA). 3. Moving Average Convergence Divergence(MACD). 4. On Balance Volume(OBV). 5. Parabolic Stop and Reverse(PSAR). 6. Relative Strength Index(RSI). 7. Average Directional Index(ADX). 8. Bollinger Bands 9. Chaikin Money flow index. 10.Rate of Change(ROC). 11.Money Flow Index(MFI).

HermiT is reasoner for ontologies written using the Web Ontology Language (OWL). Given an OWL file, HermiT can determine whether or not the ontology is consistent, identify subsumption relationships between classes, and much more. This is the maven build of HermiT and is designed for people who wish to use HermiT from within the OWL API. It is now versioned in the main HermiT version repository, although not officially supported by the HermiT developers. The version number of this package is a composite of the HermiT version and an value representing releases of this packaged version. So, 1.3.7.1 is the first release of the mavenized version of HermiT based on the 1.3.7 release of HermiT. This package includes the Jautomata library (http://jautomata.sourceforge.net/), and builds with it directly. This library appears to be no longer under active development, and so a "fork" seems appropriate. No development is intended or anticipated on this code base.

This is the tonic look-and-feel packaged to be distributed with the SQuirreLSQL client. This pluggable look and feel is a free substitute for the default native look and feel of Swing, 'Metal', distributed under the GNU Lesser General Public License. Metal lacks both in usability and aesthetics. It contains considerable graphical noise, distracting the user from the key elements of the GUI. Tonic, on the other hand, tries to provide a clean, balanced look and an improved feel. Tonic is available free of charge both for commercial and non-commercial applications. It lends a professional touch and a very tidy and clean interface to your Swing based applications.

How many classes does it take to make a cache? 60? 80? You might think so if you look at the other caches on the market. Ashkay is a streamlined, simple cache that in many ways is more powerful than the other mainstream caches. Ashkay is a strategy based caching tool. In most cases, you might be using a configuration file to tell the cache what rules it should obey. Or, you might just be setting properties on the cache. I have never liked this model as it limits me, the user of the cache to strategies the developer decided were important. Instead, Ashkay lets you choose the strategy(ies) to use when caching certain objects. Of course, a few of the most handy strategies are pre-packaged, but implementing a new one is a simple as can be. Ashkay is a fork of <a href="http://xot.sf.net">xot</a> caching code. Made more sense on its own.

HermiT is reasoner for ontologies written using the Web Ontology Language (OWL). Given an OWL file, HermiT can determine whether or not the ontology is consistent, identify subsumption relationships between classes, and much more. This is the maven build of HermiT and is designed for people who wish to use HermiT from within the OWL API. It is not officially supported by the HermiT development team, but was built initially for use with the Clojure-OWL library. It is built using the HermiT source tree without modification. There have been some additions to the test source tree to account for differences between the maven and ant environment; these are small and (hopefully) maintainable. The version number of this package is a composite of the HermiT version and an value representing releases of this packaged version. So, 1.3.7.1 is the first release of the mavenized version of HermiT based on the 1.3.7 release of HermiT. This package includes the Jautomata library (http://jautomata.sourceforge.net/), and builds with it directly. This library appears to be no longer under active development, and so a "fork" seems appropriate. No development is intended or anticipated on this code base.

Axis2 is an effort to re-design and totally re-implement both Axis/Java and (eventually) Axis/C++ on a new architecture. Evolving from the now standard "handler chain" model which Axis1 pioneered, Axis2 is developing a more flexible pipeline architecture which can yet be managed and packaged in a more organized manner. This new design acknowledges the maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging, WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time Axis1 was designed, while it was fully expected that other protocols such as WS-ReliableMessaging would be built on top of it, there was not a proper extension architecture defined to enable clean composition of such layers. Thus, one of the key motivations for Axis2 is to provide a clean and simple environment for like Apache Sandesha and Apache WSS4J to layer on top of the base SOAP system. Another driving force for Axis2 as well as the move away from RPC oriented Web services towards more document-oriented, message style asynchronous service interactions. The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP Infoset representation on top of that. The XML Infoset representation provides a JDOM-like simple API but is built on a deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM is that it allows one to stop building the XML tree and just access the pull stream directly; thus enabling both maximum flexibility and maximum performance. This approach allows us to support multiple levels of abstraction for consuming and offering Web services: using plain AXIOM, using generated code and statically data-bound data types and so on. At the time of Axis1's design, RPC-style, synchronous, request-response interactions were the order of the day for Web services. Today service interactions are much more message -oriented and exploit many different message exchange patterns. The Axis2 engine architecture is careful to not build in any assumptions of request-response patterns to ensure that it can be used easily to support arbitrary message exchange patterns.