edgent-dev mailing list archives

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

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

Christofer Dutz commented on EDGENT-440:
----------------------------------------

The change doesn't delete what has been deployed, it just prevents new deployments.

I even have a test-case that tests this in the integration-tests of the plugin itself.

> 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