4634ebc56c
changes have been battle tested with DNA/Loom.
Mauro's comments are attached for posterity:
---
attached is a first crack that incorporates the release functionality
currently in DNA and Loom distribution modules.
Two types of distributions:
- bin: this requires user customisation - uses dependency properties to
assign a category to a dependency and via a property
Eg, maven.release.distribution.categories=shared:lib,tools:tools/lib
tells it to place any "shared" dependency in path lib/ and
"tools" dependendency in tools/lib.
User can postGoal release:setup-distribution-bin to add any further
content to distribution.
- src: uses SCM plugin out of a box :-) works quite well IMO.
distribution artifact names are customisable but default to
${maven.final.name}-[bin|src].[tar.gz|zip]
Patch has documentation updated - so feel free to browse,
and let me if too scarse or patch.
If you create an issue in jira I can also attach the patch to it.
(I'm not sure If I can create the issue myself on maven project)
Further work would include incorporating the wrapper exes for the
release,�� but perhaps that's better done via a separate plugin.
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114219 13f79535-47bb-0310-9956-ffa450edef68
57 lines
1.7 KiB
XML
57 lines
1.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
<document>
|
|
<properties>
|
|
<title>Maven Release Plug-in Properties</title>
|
|
</properties>
|
|
<body>
|
|
<section name="Maven Release Plug-in Settings">
|
|
<table>
|
|
<tr>
|
|
<th>Property</th>
|
|
<th>Optional?</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.release.name.bin</td>
|
|
<td>Yes</td>
|
|
<td>The name of the binary release file.
|
|
Defaults to <code>${pom.artifactId}-${pom.currentVersion}-bin</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.release.name.src</td>
|
|
<td>Yes</td>
|
|
<td>The name of the source release file.
|
|
Defaults to <code>${pom.artifactId}-${pom.currentVersion}-src</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.release.distribution.categories</td>
|
|
<td>Yes</td>
|
|
<td>The categories and relative paths of the dependencies to
|
|
be included in the release. A list of category:path
|
|
pairs, eg <code>shared:lib,tools:tools/lib</code>, where the
|
|
category is set via dependency properties:
|
|
<source><![CDATA[
|
|
<dependency>
|
|
<groupId>[groupId]</groupId>
|
|
<artifactId>[artifactId]</artifactId>
|
|
<version>[version]</version>
|
|
<properties>
|
|
<category>shared</category>
|
|
</properties>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>[anotherGroupId]</groupId>
|
|
<artifactId>[anotherArtifactId]</artifactId>
|
|
<version>[anotherVersion]</version>
|
|
<properties>
|
|
<category>tools</category>
|
|
</properties>
|
|
</dependency>
|
|
]]></source>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
</body>
|
|
</document> |