Hi Jeff,
Agree to 4: I can't see a problem with adding this patch now, including
it in AR2 then patching it later if need be.
Jeff Ramsdale (JIRA) wrote:
[ https://issues.apache.org/jira/browse/RIVER-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758740#action_12758740 ]
Jeff Ramsdale commented on RIVER-317:
-------------------------------------
I wouldn't swear they are perfect, but I hope they are a good start. Would love
to have them validated by someone. Some questions:
1) What is the process for applying these poms to the artifacts and rolling
them out?
2) Can we set up snapshots to deploy too, with CI? (optional, to start)
3) Is there anyone who is able to validate these poms before we push?
4) Rather than waiting for AR2 can we push the current artifacts now as a
test-run for a later AR2 push? That gets the artifacts out there so they can be
tested by downstream consumers.
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: AR2, AR3
Reporter: Jeff Ramsdale
Fix For: AR2
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/<[email protected]>
