[
https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361972#comment-16361972
]
Christofer Dutz commented on EDGENT-440:
----------------------------------------
I just checked the job that handles the deployment of snapshots and it
correctly stops deploying the test-jars:
[https://builds.apache.org/view/E-G/view/Edgent/job/edgent-pipeline/job/develop/40/consoleFull]
We might need a manual cleanup of the snapshots though to completely get rid of
old test-jars. I just double-checked that and I do not seem to have permissions
to delete snapshots. So I think we should ask infra to delete the entire Edgent
branch of the "snapshot" repo. Then I'll re-deploy the new plugin and then with
the next build the test-jars should be history.
> 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)
