Description

<dependency>
    <groupId>io.atomix.catalyst</groupId>
    <artifactId>catalyst-kryo</artifactId>
    <version>1.2.1</version>
</dependency>

<!--
  ~ Copyright 2015 the original author or authors.
  ~
  ~ Licensed under the Apache License, Version 2.0 (the "License");
  ~ you may not use this file except in compliance with the License.
  ~ You may obtain a copy of the License at
  ~
  ~ http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing, software
  ~ distributed under the License is distributed on an "AS IS" BASIS,
  ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  ~ See the License for the specific language governing permissions and
  ~ limitations under the License
  -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>io.atomix.catalyst</groupId>
    <artifactId>catalyst-parent</artifactId>
    <version>1.2.1</version>
  </parent>

  <packaging>bundle</packaging>
  <artifactId>catalyst-kryo</artifactId>
  <name>Catalyst Kryo Serializer</name>

  <properties>
    <kryo.version>3.0.3</kryo.version>
  </properties>

  <dependencies>
    <dependency>
      <groupId>io.atomix.catalyst</groupId>
      <artifactId>catalyst-serializer</artifactId>
      <version>${project.version}</version>
    </dependency>
    <dependency>
      <groupId>com.esotericsoftware</groupId>
      <artifactId>kryo</artifactId>
      <version>${kryo.version}</version>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <!-- This plugin forces the generation of jar containing streaming test classes, so that the tests 
        classes of external modules can use them. The two execution profiles are necessary - first one for 'mvn 
        package', second one for 'mvn test-compile'. Ideally, 'mvn compile' should not compile test classes and 
        therefore should not need this. However, an open Maven bug (http://jira.codehaus.org/browse/MNG-3559) 
        causes the compilation to fail if streaming test-jar is not generated. Hence, the second execution profile 
        for 'mvn test-compile'. -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <executions>
          <execution>
            <goals>
              <goal>test-jar</goal>
            </goals>
          </execution>
          <execution>
            <id>test-jar-on-test-compile</id>
            <phase>test-compile</phase>
            <goals>
              <goal>test-jar</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>