commit | 93f482aa447e5f63c3e3406f05e328404ac143ba | [log] [tgz] |
---|---|---|
author | Mike Walch <mwalch@gmail.com> | Fri Jun 17 17:13:20 2016 -0400 |
committer | Mike Walch <mwalch@gmail.com> | Fri Jun 17 17:13:20 2016 -0400 |
tree | ab18da594b865496c4db03541705e7f283870f46 | |
parent | 4e332ef70bff37ab9ca5ee1f507a90479cdc14a2 [diff] |
Delete AUTHORS file, added DISCLAMER & NOTICE, updated project website links
Common code for Apache Fluo application developers.
Recipes have common needs that are broken down into the following reusable components.
Fluo Recipes provides multiple jars. The primary reason its separated into multiple jars is to avoid pushing unneeded dependencies on users. For example there is a Fluo Recipes spark module that depends on Spark. If an application does not need to use Spark, then it can easily avoid a transitive dependency on Spark.
Below are Maven dependencies for Fluo Recipes.
<properties> <fluo-recipes.version>1.0.0-beta-2</fluo-recipes.version> </properties> <dependencies> <!-- Recipes core only has a transitive dependency on the Fluo API --> <dependency> <groupId>org.apache.fluo</groupId> <artifactId>fluo-recipes-core</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency provides the default Fluo Recipes serialization mechanism, which is based on Kryo --> <dependency> <groupId>org.apache.fluo</groupId> <artifactId>fluo-recipes-kryo</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency assist w/ intergrating Accumulo and Fluo --> <dependency> <groupId>org.apache.fluo</groupId> <artifactId>fluo-recipes-accumulo</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency assist w/ intergrating Spark and Fluo --> <dependency> <groupId>org.apache.fluo</groupId> <artifactId>fluo-recipes-spark</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency helps when write Fluo intergeration test. --> <dependency> <groupId>org.apache.fluo</groupId> <artifactId>fluo-recipes-test</artifactId> <version>${fluo-recipes.version}</version> <scope>test</scope> </dependency> </dependencies>