tag | f3752d8cd436a84cc7c0ca8ef71e550d023f5c7a | |
---|---|---|
tagger | Mike Walch <mwalch@gmail.com> | Tue Mar 29 12:46:18 2016 -0400 |
object | b418b6495a41b145f9146063008d8d8b830f343a |
Creating signed tag for 1.0.0-beta-2 release
tag | b418b6495a41b145f9146063008d8d8b830f343a | |
---|---|---|
tagger | Mike Walch <mwalch@gmail.com> | Tue Mar 29 11:59:21 2016 -0400 |
object | 0c86f6e152047b2f70045a809c5db8f5d7e3e899 |
[maven-release-plugin] copy for tag fluo-recipes-parent-1.0.0-beta-2
commit | 0c86f6e152047b2f70045a809c5db8f5d7e3e899 | [log] [tgz] |
---|---|---|
author | Mike Walch <mwalch@gmail.com> | Tue Mar 29 11:59:21 2016 -0400 |
committer | Mike Walch <mwalch@gmail.com> | Tue Mar 29 11:59:21 2016 -0400 |
tree | f718d1c9149b63f41415603bdc00553b84d67eac | |
parent | df008a6a6b87d088b5089ca15faac066b482a0be [diff] |
[maven-release-plugin] prepare release fluo-recipes-parent-1.0.0-beta-2
Common code for 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>io.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>io.fluo</groupId> <artifactId>fluo-recipes-kryo</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency assist w/ intergrating Accumulo and Fluo --> <dependency> <groupId>io.fluo</groupId> <artifactId>fluo-recipes-accumulo</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency assist w/ intergrating Spark and Fluo --> <dependency> <groupId>io.fluo</groupId> <artifactId>fluo-recipes-spark</artifactId> <version>${fluo-recipes.version}</version> </dependency> <!--optional dependency helps when write Fluo intergeration test. --> <dependency> <groupId>io.fluo</groupId> <artifactId>fluo-recipes-test</artifactId> <version>${fluo-recipes.version}</version> <scope>test</scope> </dependency> </dependencies>