commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSSITE-95) Add mojo to commons-build-plugin to move dists out of deployment to nexus.
Date Fri, 03 Nov 2017 15:37:00 GMT

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

Benedikt Ritter commented on COMMONSSITE-95:
--------------------------------------------

Awesome you're working on this. I remember us talking about it at ApacheCon in Miami. I'm
excited to see what we can put together here.

> Add mojo to commons-build-plugin to move dists out of deployment to nexus.
> --------------------------------------------------------------------------
>
>                 Key: COMMONSSITE-95
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-95
>             Project: Commons All
>          Issue Type: New Feature
>    Affects Versions: 1.7
>            Reporter: Rob Tompkins
>            Assignee: Rob Tompkins
>            Priority: Normal
>
> Currently we have to log into the nexus after doing a release deployment and delete the
{{-bin.tar.gz}}, the {{-bin.zip}}, the {{-src.tar.gz}}, the {{-src.zip}}, and their signature
files. We want this to not happen automatically. 
> Further, it could be nice if these artifacts were automatically staged in the dev distribution
svn repo, but this may require a new JIRA. For now I will concern myself with creating a separate
directory under {{./target}} that will contain the dists.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message