Download JAR files tagged by necessary with all dependencies

Avalon Excalibur's DataSource package allows you to manage pooled connections in one of two ways. You can have the package handle it for you, or you can use a J2EE server's DataSource management. It provides the same kind of access regardless of which method you choose, since they are obtained through Avalon's Component Manager infrastructure. The DataSource package requires that you load the necessary driver classes at init time, but it will take care of all necessary issues from there.

Avalon Excalibur's DataSource package allows you to manage pooled connections in one of two ways. You can have the package handle it for you, or you can use a J2EE server's DataSource management. It provides the same kind of access regardless of which method you choose--since they are obtained through Avalon's Component Manager infrastructure. The DataSource package requires that you load the necessary driver classes at init time, but it will take care of all necessary issues from there.

Provides all necessary resources for a Java project to enforce the coding style that I am using in my lectures about software development at Munich University of Applied Sciences and in all of my open source projects. It configures several static analysis tools for Maven and IntelliJ. Moreover, it provides some sample classes that already use this style guide. This classes can be used as such but are not required in this project. These classes also use some additional libraries that are included using the Maven dependency mechanism. If the sample classes are deleted then the dependencies can be safely deleted, too.

Jadex XML is an XML data binding framework for Java and also for other representations. The main idea of Jadex XML is that neither the XML-Schema on the one side nor the Java classes on the other side should define other binding. Instead, a separate mapping between both is used as a mediation. This allows designing the XML representation independent of the Java side but still being able to connect both as desired. This idea was first put forward by the JiBX data binding framework. Jadex XML pushes it further by combining it with the configuration by exception principle. The framework can detect obvious correspondences between both sides automatically and only needs configuration information when translations are necessary. The configuration information is currently specified directly in form of Java configuration classes.

Samply.Common.MDRFaces is a Java Server Faces library which eases the user interface design of web applications where the respective data model relies on well defined data elements. Especially in case of systems for electronic data capturing, where the necessary data model is not known beforehand and can even vary over time, the user interface has to be easily adjustable. This often means the user instead of the developer designs the various forms for data entry and therefore an easy to use mechanism has to be provided. By using Samply.MDRFaces the developer can focus on the implementation of that mechanism, e.g. some editor component, but does not have to cope with the visualization of every single data element as for that is taken care of automatically.

Jadex XML is an XML data binding framework for Java and also for other representations. The main idea of Jadex XML is that neither the XML-Schema on the one side nor the Java classes on the other side should define other binding. Instead, a separate mapping between both is used as a mediation. This allows designing the XML representation independent of the Java side but still being able to connect both as desired. This idea was first put forward by the JiBX data binding framework. Jadex XML pushes it further by combining it with the configuration by exception principle. The framework can detect obvious correspondences between both sides automatically and only needs configuration information when translations are necessary. The configuration information is currently specified directly in form of Java configuration classes.

Tool used to analyze a set of classes and determine on what other classes they directly or indirectly depend. Typically this tool is used to compute the necessary and sufficient set of classes to include in a JAR file, for use in the class path of a client or service, or for use in the codebase of a client or service. The tool starts with a set of "root" classes and recursively computes a dependency graph, finding all of the classes referenced directly by the root classes, finding all of the classes referenced in turn by those classes, and so on, until no new classes are found or until classes that are not of interest are found. The normal output of the tool is a list of all of the classes in the dependency graph. The output from this command can be used as input to the jar tool, to create a JAR file containing precisely those classes.

This library provides the necessary implementations to screen the following patterns: Bullish Belt Hold Bearish Belt Hold Hammer Hanging Man Southern Doji Northern Doji Gapping Up Doji Gapping Down Doji Takuri Line One Candle Shooting Star Bullish Strong Line Bearish Strong Line Bullish Harami Bearish Harami Bullish Engulfing Bearish Engulfing Bullish Kicking Bearish Kicking Matching Low Matching High Bullish Harami Cross Bearish Harami Cross Bullish Doji Star Bearish Doji Star Dark Cloud Cover Piercing Line Descending Hawk Homing Pigeon Bullish Abandoned Baby Bearish Abandoned Baby Three Inside Up Three Inside Down Three Outside Up Three Outside Down Three White Soldiers Three Black Crows Morning Doji Star Evening Doji Star Morning Star Evening Star Upside Tasuki Gap Downside Tasuki Gap Bullish Side by Side White Lines Bearish Side by Side White Lines Rising Three Method

zlib is designed to be a free, general-purpose, legally unencumbered -- that is, not covered by any patents -- lossless data-compression library for use on virtually any computer hardware and operating system. The zlib data format is itself portable across platforms. Unlike the LZW compression method used in Unix compress(1) and in the GIF image format, the compression method currently used in zlib essentially never expands the data. (LZW can double or triple the file size in extreme cases.) zlib's memory footprint is also independent of the input data and can be reduced, if necessary, at some cost in compression.

Customizable cruft-free Scala archetype. Options: -sourceFolders: [all-in-src-java, scala-only, both-split-src]. DEFAULT: all-in-src-java. --all-in-src-java: Scala and Java code are both in src/main/java (same for test). Plays nicely with IDEs. --scala-only: only src/main/scala set up, and set as source folder. --both-split-src: both src/main/java and src/main/scala. Can play merry havock with IDEs, so not the default. -testLibrary: [scalatest, specs2, scalacheck-only, junit-only]. DEFAULT: scalatest. --scalatest: adds Scalatest AND Scalacheck AND JUnit for most of your testing needs. --specs2: adds specs2 AND Scalacheck AND JUnit. --scalacheck-junit: adds Scalacheck AND JUnit. --junit-only: adds JUnit ONLY. -scalaVersion: 2.10.x+. DEFAULT: 2.11.2. *The Scala tool version is generated automatically. *Some Scala versions may not be compatible with selected test library versions. Adjust as necessary.