[ 
https://issues.apache.org/jira/browse/UNOMI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Serge Huber reassigned UNOMI-1011:
----------------------------------

      Assignee: Serge Huber
    Resolution: Fixed

> The release publishes an extra build cache artifact
> ---------------------------------------------------
>
>                 Key: UNOMI-1011
>                 URL: https://issues.apache.org/jira/browse/UNOMI-1011
>             Project: Apache Unomi
>          Issue Type: Task
>    Affects Versions: unomi-4.0.0
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Minor
>             Fix For: unomi-4.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> h3. Summary
> The 4.0.0 staging repository contains an artifact named 
> unomi-4.0.0-buildcache.jar. It is an empty file used only during the build, 
> and 3.0.1 did not publish it. It started being published when UNOMI-981 
> turned deployment of the package module back on.
> The goal of this ticket is that the release publishes only real artifacts.
> h3. Ways to explore
> * Keep the file for the build, but do not attach it to the published 
> artifacts.
> * Remove the workaround if it is no longer needed.
> h3. How to test
> Manual check: run a deploy to a local repository. Check that no buildcache 
> artifact is published and that the distribution is still published.
> Automated check to add:
> * A step in the release audit script that lists the staged artifacts and 
> fails if a buildcache artifact is present, or if the distribution archives 
> are missing. This keeps UNOMI-981 fixed and prevents this problem from coming 
> back.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to