You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2008/03/05 21:45:40 UTC
[jira] Resolved: (PLUTO-472) Fix Pluto Maven 2 release assemblies
so they actually work.
[ https://issues.apache.org/jira/browse/PLUTO-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger resolved PLUTO-472.
----------------------------------
Resolution: Fixed
Assembly descriptors have been cleaned up to use <moduleSets> and use component descriptors to reduce copy-and-paste of redundant assembly information. The ant build used to download tomcat had its documentation updated. Plugins used in the release (assembly, gpg, remote-resources, release) had their versions pegged if they didn't already.
Running:
mvn -Passembly,build-assemblies clean site verify assembly:attached
from the root project
* produces assemblies in target/assembly/out
* results in all artifacts (POM files and jars/wars) being signed (do a find for *.asc after the assembly completes)
* results in complete NOTICE and LICENSE files included in each artifact.
> Fix Pluto Maven 2 release assemblies so they actually work.
> -----------------------------------------------------------
>
> Key: PLUTO-472
> URL: https://issues.apache.org/jira/browse/PLUTO-472
> Project: Pluto
> Issue Type: Improvement
> Affects Versions: 1.1.4
> Reporter: Elliot Metsger
> Assignee: Elliot Metsger
> Fix For: 1.1.5
>
>
> Fix Pluto Maven 2 release assemblies so they actually work:
> 1) Update the assembly descriptors
> 2) Peg release-related plugins (antrun, assembly, gpg) to specific versions
> 2) Document assembly release process on the wiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.