You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2010/11/13 00:56:16 UTC
[jira] Updated: (RIVER-317) Deploy Apache River artifacts to Maven
repositories (both release and snapshot)
[ https://issues.apache.org/jira/browse/RIVER-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-317:
----------------------------------
Fix Version/s: (was: River_2.1.3)
AR4
Issue resolution delayed until following release
> Deploy Apache River artifacts to Maven repositories (both release and snapshot)
> -------------------------------------------------------------------------------
>
> Key: RIVER-317
> URL: https://issues.apache.org/jira/browse/RIVER-317
> Project: River
> Issue Type: Task
> Components: Web site and infrastructure
> Affects Versions: River_2.1.2, River_2.1.3
> Reporter: Jeff Ramsdale
> Fix For: AR4
>
> Attachments: river-poms.patch
>
>
> It would be valuable if Apache River artifacts were deployed to a Maven repository upon release. It would be even better if snapshot builds were also deployed to a snapshot repository by Hudson.
> See thread: http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200908.mbox/<e2...@mail.gmail.com>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.