cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Date Mon, 24 Jan 2011 20:46:43 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985973#action_12985973
] 

Eric Evans commented on CASSANDRA-2017:
---------------------------------------

Question: why does this patch copy {{maven-ant-tasks-2.1.1.jar}} into the binary release artifact?

Also, I wonder if it's the best thing to be making this sort of change in a stable release.

+1 on the general approach though.  I think.

> 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.


Mime
View raw message