You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2011/01/20 17:31:43 UTC
[jira] Updated: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated CASSANDRA-2017:
----------------------------------------
Attachment: CASSANDRA-2017-initial-patch.patch
This is not ready to be applied yet. Only a first stab. I need to optimize somewhat. Attaching so that I can get feedback.
Note if you are behind a proxy you will need to have ANT configured for the proxy or use ant-autoproxy
> Replace ivy withmaven-ant-tasks
> -------------------------------
>
> Key: CASSANDRA-2017
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2017
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.1
> Reporter: Stephen Connolly
> Attachments: CASSANDRA-2017-initial-patch.patch
>
>
> Replace ivy with maven-ant-tasks.
> Three main reasons:
> 1. In order to deploy cassandra to maven central, we will need to use maven-ant-tasks anyway (as ivy does not generate correct poms)
> 2. In order to generate gpg signatures using ivy, we need to bootstrap a second ivy taskdef or use multiple <get> tasks to download bouncycastle. Maven-ant-tasks does not require this.
> 3. Allows consolidating the dependency information in one place. Rather than having duplication with the maven-ant-tasks for deploy to central
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.