[
https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326532#comment-16326532
]
Dale LaBossiere commented on EDGENT-440:
----------------------------------------
Forgot to mention that I added buildTools/check_jars.sh. The script checks
that LICENSE,... metadata are present in jars/wars. It can be run against a
built workspace (e.g., pre-release) or against artifacts retrieved by
samples/get-edgent-jars.
What's missing is some tool that can pull down the full set of RC artifacts
staged in Nexus to verify them, and to verify there are no missing or extra
artifacts present.
> Adjust "release" processing so only desired artifacts are uploaded to
> Nexus/MavenCentral
> ----------------------------------------------------------------------------------------
>
> Key: EDGENT-440
> URL: https://issues.apache.org/jira/browse/EDGENT-440
> Project: Edgent
> Issue Type: Task
> Components: Miscellaneous
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
> Priority: Major
>
> The release process tooling/config for 1.2.0 uploaded some unwanted artifacts
> to Nexus and they had to be manually removed before continuing the release.
> Adjust the “deploy” processing so as to upload only the desired artifacts to
> nexus (no “test” jars, no “distribution” bundles, no “test projects)
> We really should have some “release validation” processing, that anyone can
> run as part of validating a releasee, for checking the staged nexus artifacts
> * have exactly the expected set of jars/wars/pom-only
> * the jars have exactly the expected/required (jar/war dependent)
> LICENSE, NOTICE and DISCLAIMER and contain a DEPENDENCIES
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
