grinder
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>net.sf.grinder</groupId>
<artifactId>grinder</artifactId>
<version>3.11</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<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">
<modelVersion>4.0.0</modelVersion>
<artifactId>grinder</artifactId>
<packaging>jar</packaging>
<name>${project.artifactId}</name>
<url>http://grinder.sourceforge.net</url>
<description>The Grinder load testing framework. The Grinder is a load testing
framework that makes it easy to run a distributed test using many load
injector machines. Test scripts are written in Jython or Clojure. HTTP
scripts can be recorded easily from a browser session. </description>
<parent>
<groupId>net.sf.grinder</groupId>
<artifactId>grinder-parent</artifactId>
<version>3.11</version>
</parent>
<dependencies>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-dcr-agent</artifactId>
<version>3.11</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-http</artifactId>
<version>3.11</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-console-service</artifactId>
<version>3.11</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-swing-console</artifactId>
<version>3.11</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<!-- Indexing doesn't allow for our grinder-patch.jar, and fails to
index ring-middleware-format.jar for some reason. -->
<index>false</index>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<!-- Unfortunately, the maven archive plugin does not provide a
way to filter the list of dependencies used to generate the
classpath. This means the classpath has redundant entries
for things we shade into the jar.
-->
<!-- On the other hand, we've placed the DCR agent in the
"compile" scope, not "provided", specifically so it's in the
manifest classpath and its classes can be loaded if the
agent is not loaded. -->
<addClasspath>true</addClasspath>
</manifest>
<manifest-entries>
<!-- Provide an easy way to provide temporary patches without
modifying the classpath. -->
<!-- Add jython.jar up front, so users can continue to override
by dropping a new version into the lib directory. -->
<Class-Path>grinder-patch.jar jython.jar</Class-Path>
</manifest-entries>
</archive>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.portals.jetspeed-2</groupId>
<artifactId>jetspeed-unpack-maven-plugin</artifactId>
<executions>
<execution>
<id>copy-xsl</id>
<goals>
<goal>unpack</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<unpack>
<artifact>${project.groupId}:grinder-http:jar</artifact>
<overwrite>true</overwrite>
<resources>
<resource>
<destination>unpacked/etc</destination>
<flat>true</flat>
<include>**/*.xsl</include>
</resource>
</resources>
</unpack>
</configuration>
</execution>
<execution>
<id>copy-xsd</id>
<goals>
<goal>unpack</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<unpack>
<artifact>${project.groupId}:grinder-xmlbeans:jar</artifact>
<overwrite>true</overwrite>
<resources>
<resource>
<destination>unpacked/etc</destination>
<flat>true</flat>
<include>**/*.xsd</include>
</resource>
</resources>
</unpack>
</configuration>
</execution>
<execution>
<id>copy-license</id>
<goals>
<goal>unpack</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<unpack>
<artifact>${project.groupId}:grinder-httpclient:jar</artifact>
<overwrite>true</overwrite>
<resources>
<resource>
<destination>unpacked</destination>
<flat>true</flat>
<include>META-INF/LICENSE</include>
<name>LICENSE-HTTPClient</name>
</resource>
</resources>
</unpack>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-http</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-httpclient</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>grinder-xmlbeans</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptors>
<descriptor>src/main/assembly/assembly.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</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