edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
Date Tue, 20 Feb 2018 20:12:00 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370557#comment-16370557
] 

Dale LaBossiere commented on EDGENT-440:
----------------------------------------

These unwanted files are still present in a newly generated release snapshot:
 * .../*-<ver>-tests.jar.asc   # the signature file of the no longer present test
jar files
 * edgent-parent/.../edgent-parent-<ver>-source-release.*

> 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)

Mime
View raw message