jar:test-jar – Apache Maven JAR Plugin (original) (raw)

Full name:

org.apache.maven.plugins:maven-jar-plugin:3.5.0:test-jar

Description:

Build a JAR of the test classes for the current project.

Attributes:

Required Parameters

Name Type Since Description
File - Directory containing the generated JAR.Default: ${project.build.directory}
File - Directory containing the test classes and resource files that should be packaged into the JAR.Default: ${project.build.testOutputDirectory}

Optional Parameters

Name Type Since Description
boolean 3.4.0 If set to false, the files and directories that by default are excluded from the resulting archive, like .gitignore, .cvsignore etc. will be included. This means all files like the following will be included. Misc: **/*~, **/#*#, **/.#*, **/%*%, **/._* CVS: **/CVS, **/CVS/**, **/.cvsignore RCS: **/RCS, **/RCS/** SCCS: **/SCCS, **/SCCS/** VSSercer: **/vssver.scc MKS: **/project.pj SVN: **/.svn, **/.svn/** GNU: **/.arch-ids, **/.arch-ids/** Bazaar: **/.bzr, **/.bzr/** SurroundSCM: **/.MySCMServerInfo Mac: **/.DS_Store Serena Dimension: **/.metadata, **/.metadata/** Mercurial: **/.hg, **/.hg/** Git: **/.git, **/.git/** Bitkeeper: **/BitKeeper, **/BitKeeper/**, **/ChangeSet, **/ChangeSet/** Darcs: **/_darcs, **/_darcs/**, **/.darcsrepo, **/.darcsrepo/****/-darcs-backup*, **/.darcs-temp-mail See also: DEFAULTEXCLUDESDefault: true
MavenArchiveConfiguration - The archive configuration to use. See Maven Archiver Reference.
boolean 3.5.0 Specifies whether to attach the jar to the projectDefault: trueUser Property: maven.jar.attach
String - Classifier to use for test-jar.Default: tests
boolean 3.4.0 If the JAR contains the META-INF/versions directory it will be detected as a multi-release JAR file ("MRJAR"), adding the Multi-Release: true attribute to the main section of the JAR MANIFEST.MF.Default: trueUser Property: maven.jar.detectMultiReleaseJar
String[] - List of files to exclude. Specified as fileset patterns which are relative to the input directory whose contents is being packaged into the JAR.
boolean - Require the jar plugin to build a new JAR even if none of the contents appear to have changed. By default, this plugin looks to see if the output jar exists and inputs have not changed. If these conditions are true, the plugin skips creation of the jar. This does not work when other plugins, like the maven-shade-plugin, are configured to post-process the jar. This plugin can not detect the post-processing, and so leaves the post-processed jar in place. This can lead to failures when those plugins do not expect to find their own output as an input. Set this parameter to true to avoid these problems by forcing this plugin to recreate the jar every time. Starting with 3.0.0 the property has been renamed from jar.forceCreation to maven.jar.forceCreation.Default: falseUser Property: maven.jar.forceCreation
String[] - List of files to include. Specified as fileset patterns which are relative to the input directory whose contents is being packaged into the JAR.
String 3.2.0 Timestamp for reproducible output archive entries, either formatted as ISO 8601 extended offset date-time (e.g. in UTC such as '2011-12-03T10:15:30Z' or with an offset '2019-10-05T20:37:42+06:00'), or as an int representing seconds since the epoch (like SOURCE_DATE_EPOCH).Default: ${project.build.outputTimestamp}
boolean - Set this to true to bypass test-jar generation. Its use is NOT RECOMMENDED, but quite convenient on occasion.User Property: maven.test.skip
boolean - Skip creating empty archives.Default: false
boolean - Deprecated.For version 3.0.0 this parameter is only defined here to break the build if you use it!Using this property will fail your build cause it has been removed from the plugin configuration. See the menu entry Using Your Own Manifest File for the plugin.Default: falseUser Property: jar.useDefaultManifestFile

Parameter Details

If set to false, the files and directories that by default are excluded from the resulting archive, like .gitignore, .cvsignore etc. will be included. This means all files like the following will be included.

See also: DEFAULTEXCLUDES

Specifies whether to attach the jar to the project

Classifier to use for test-jar.

If the JAR contains the META-INF/versions directory it will be detected as a multi-release JAR file ("MRJAR"), adding the Multi-Release: true attribute to the main section of the JAR MANIFEST.MF.

List of files to exclude. Specified as fileset patterns which are relative to the input directory whose contents is being packaged into the JAR.

Require the jar plugin to build a new JAR even if none of the contents appear to have changed. By default, this plugin looks to see if the output jar exists and inputs have not changed. If these conditions are true, the plugin skips creation of the jar. This does not work when other plugins, like the maven-shade-plugin, are configured to post-process the jar. This plugin can not detect the post-processing, and so leaves the post-processed jar in place. This can lead to failures when those plugins do not expect to find their own output as an input. Set this parameter to

true

to avoid these problems by forcing this plugin to recreate the jar every time.
Starting with 3.0.0 the property has been renamed from jar.forceCreation to maven.jar.forceCreation.

List of files to include. Specified as fileset patterns which are relative to the input directory whose contents is being packaged into the JAR.

Directory containing the generated JAR.

Timestamp for reproducible output archive entries, either formatted as ISO 8601 extended offset date-time (e.g. in UTC such as '2011-12-03T10:15:30Z' or with an offset '2019-10-05T20:37:42+06:00'), or as an int representing seconds since the epoch (like SOURCE_DATE_EPOCH).

Set this to true to bypass test-jar generation. Its use is NOT RECOMMENDED, but quite convenient on occasion.

Skip creating empty archives.

Directory containing the test classes and resource files that should be packaged into the JAR.

Deprecated.
For version 3.0.0 this parameter is only defined here to break the build if you use it!

Using this property will fail your build cause it has been removed from the plugin configuration. See the menu entry Using Your Own Manifest File for the plugin.