[jira] [Updated] (UIMA-2008) Don't attach large distribution artifacts for uima-as builds, but sign them for releasing

["Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>]

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

Richard Eckart de Castilho updated UIMA-2008:
---------------------------------------------
    Labels: Stale  (was: )

This issue is marked as "stale" due to inactivity for 5 years or longer. If no further activity is detected on this issue, it is scheduled be closed as 'unresolved' in 3 months time from now (Dec 2016).

> Don't attach large distribution artifacts for uima-as builds, but sign them for releasing
> -----------------------------------------------------------------------------------------
>
>                 Key: UIMA-2008
>                 URL: https://issues.apache.org/jira/browse/UIMA-2008
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Priority: Minor
>              Labels: Stale
>
> The build process for distributions builds large binary assembly artifacts; the build process at the top level under profile apache-release builds large source-release.zip files.  These files, for the uima-as distribution, are made available after release on our download pages, and use the non-maven Apache distribution mirroring system.
> These files probably should not be "attached" in the maven sense for uploading to maven central upon release; they will just waste space.  
> Change the build so these are not "attached".   Find another way to get these unattached things "signed" (currently done in the deploy step).  One way is to use maven antrun plugin to do an ant exec of the gpg command on the artifact; there may be other ways.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)