uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] Commented: (UIMA-2008) Don't attach large distribution artifacts for uima-as builds, but sign them for releasing
Date Thu, 20 Jan 2011 16:33:47 GMT

    [ https://issues.apache.org/jira/browse/UIMA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984266#action_12984266

Marshall Schor commented on UIMA-2008:

I like how you generate also the vote.txt ! :-)  

So, it looks like maybe the best solution is:

1) override deploy to skip deploying, but leave the assembly artifacts "attached".  The common
apache pom, in its apache-release profile, invokes gpg maven plugin which then signs all "attached"
2) use antrun to generate the checksums

> 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
> 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 is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message