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:29:43 UTC
[jira] Created: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
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
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.
[jira] Updated: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Stephen Connolly (JIRA)" <ji...@apache.org>.
[ 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.patch
Final patch that includes a fix for CASSANDRA-2046
> 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, CASSANDRA-2017.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.
[jira] Assigned: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani reassigned CASSANDRA-2017:
-----------------------------------------
Assignee: Stephen Connolly
> 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
> Assignee: Stephen Connolly
> Fix For: 0.7.1
>
> Attachments: CASSANDRA-2017-initial-patch.patch, CASSANDRA-2017.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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985040#action_12985040 ]
T Jake Luciani commented on CASSANDRA-2017:
-------------------------------------------
I like this approach because it doesn't require maven to be installed, it removed ivy.xml and ivysettings.xml and it makes it easier to generate pom.xml for maven distribution.
> 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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Stephen Connolly (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986060#action_12986060 ]
Stephen Connolly commented on CASSANDRA-2017:
---------------------------------------------
I'll bundle the fix for CASSANDRA-2046 into this patch then
> 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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986218#action_12986218 ]
Eric Evans commented on CASSANDRA-2017:
---------------------------------------
LGTM, +1, (and I think I'm sufficiently convinced that it's OK for 0.7.1 as well).
I think tjake was planning to commit this, so I'll leave it here for the time being, until he has a chance to look it over.
Thanks Stephen.
> 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, CASSANDRA-2017.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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-2017:
----------------------------------
Reviewer: urandom
> 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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985131#action_12985131 ]
Jonathan Ellis commented on CASSANDRA-2017:
-------------------------------------------
Tested that ant release still works after realclean. On a standard build, dependency checking is dramatically faster than ivy's.
With my limited build expertise I am +0.
Jake, can you commit Monday? (To give anyone else a couple more days to review if they are so inclined.)
> 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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986412#action_12986412 ]
Hudson commented on CASSANDRA-2017:
-----------------------------------
Integrated in Cassandra-0.7 #204 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/204/])
Switch from ivy to maven-ivy-tasks to ease maven central builds.
Patch by Stephen Connolly reviewed by eevans and tjake for CASSANDRA-2017
> 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
> Assignee: Stephen Connolly
> Fix For: 0.7.1
>
> Attachments: CASSANDRA-2017-initial-patch.patch, CASSANDRA-2017.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.
[jira] Updated: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Stephen Connolly (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-2017) Replace ivy withmaven-ant-tasks
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985156#action_12985156 ]
Eric Evans commented on CASSANDRA-2017:
---------------------------------------
bq. This is not ready to be applied yet. Only a first stab
We should probably wait at least until Stephen gives it the Green Light.
> 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.