yammer-extra-parent
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>com.arpnetworking.metrics.extras</groupId>
<artifactId>yammer-extra-parent</artifactId>
<version>0.4.2</version>
</dependency><?xml version="1.0"?>
<!--
~ Copyright 2015 Groupon.com
~
~ 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/maven-v4_0_0.xsd">
<parent>
<groupId>com.arpnetworking.build</groupId>
<artifactId>arpnetworking-parent-pom</artifactId>
<version>1.0.18</version>
<relativePath />
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>com.arpnetworking.metrics.extras</groupId>
<artifactId>yammer-extra-parent</artifactId>
<packaging>pom</packaging>
<name>Metrics Client Yammer Extras</name>
<description>Extension to metrics-java-client which adapts the client for use in conjunction or in place of the Yammer metrics library.</description>
<version>0.4.2</version>
<licenses>
<license>
<name>Apache License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
<comments>A business-friendly OSS license</comments>
</license>
</licenses>
<developers>
<developer>
<id>brandonarp</id>
<name>Brandon Arp</name>
<email>barp@groupon.com</email>
<organization>Groupon</organization>
<organizationUrl>http://www.groupon.com</organizationUrl>
<roles>
<role>developer</role>
</roles>
</developer>
<developer>
<id>villekoskela</id>
<name>Ville Koskela</name>
<email>vkoskela@groupon.com</email>
<organization>Groupon</organization>
<organizationUrl>http://www.groupon.com</organizationUrl>
<roles>
<role>developer</role>
</roles>
</developer>
</developers>
<scm>
<connection>scm:git:git@github.com:ArpNetworking/metrics-yammer-extra.git</connection>
<developerConnection>scm:git:git@github.com:ArpNetworking/metrics-yammer-extra.git</developerConnection>
<url>https://github.com/arpnetworking/metrics-yammer-extra</url>
<tag>yammer-extra-parent-0.4.2</tag>
</scm>
<modules>
<module>yammer-extra</module>
<module>yammer-replace</module>
<module>yammer-shaded</module>
</modules>
<properties>
<!-- IMPORTANT: Any changes to dependencies, including versions, require
validation that the shading rules correctly resolve the transitive closure
of all non-test packages. You can validate that the transitive closure of
dependencies was covered by checking the pom file generated by the shade
plugin: dependency-reduced-pom.xml.
In general, there are two strategies for dealing with additional
dependencies:
1) If we depend on package A and it on package B but we don't use any
features that require package B we may exclude those classes from package
A and prune the dependency on package B. This will remove package B.
2) If we depend on package A and it on package B and we cannot prune the
dependency then include the package and classpath(s) for package B in the
shade plugin's mapping. This will hide package B.
-->
<!--Dependency versions-->
<findbugs.annotations.version>3.0.0</findbugs.annotations.version>
<hamcrest.version>2.0.0.0</hamcrest.version>
<junit.version>4.12</junit.version>
<metrics.client.version>0.4.2</metrics.client.version>
<mockito.version>1.10.19</mockito.version>
<slf4j.version>1.7.10</slf4j.version>
<yammer.metrics.version>2.2.0</yammer.metrics.version>
<!--Plugin versions-->
<maven.shade.plugin.version>2.4.1</maven.shade.plugin.version>
<!-- Code Coverage -->
<jacoco.check.line.coverage>1.0</jacoco.check.line.coverage>
<jacoco.check.branch.coverage>1.0</jacoco.check.branch.coverage>
</properties>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>${maven.shade.plugin.version}</version>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>com.rimerosolutions.maven.plugins</groupId>
<artifactId>wrapper-maven-plugin</artifactId>
<inherited>false</inherited>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<!-- Logging -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${slf4j.version}</version>
</dependency>
<!-- Application -->
<dependency>
<groupId>com.yammer.metrics</groupId>
<artifactId>metrics-core</artifactId>
<version>${yammer.metrics.version}</version>
</dependency>
<dependency>
<groupId>com.arpnetworking.metrics</groupId>
<artifactId>metrics-client</artifactId>
<version>${metrics.client.version}</version>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>annotations</artifactId>
<version>${findbugs.annotations.version}</version>
</dependency>
<!-- Test - General -->
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>java-hamcrest</artifactId>
<version>${hamcrest.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>${mockito.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
</dependencyManagement>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report