You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2021/03/29 13:52:00 UTC
[jira] [Comment Edited] (CASSANDRA-16391) Migrate use of
maven-ant-tasks to resolver-ant-tasks
[ https://issues.apache.org/jira/browse/CASSANDRA-16391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310656#comment-17310656 ]
Michael Semb Wever edited comment on CASSANDRA-16391 at 3/29/21, 1:51 PM:
--------------------------------------------------------------------------
PoC patch ready for earlier review
https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16391/trunk
Decisions I made in this patch
- a full migration away from maven-ant-tasks cannot be done as it is still used for writing the pom files
- …wip…
was (Author: michaelsembwever):
PoC patch ready for earlier review
https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16391/trunk
Decisions I made in this patch
- …wip
> Migrate use of maven-ant-tasks to resolver-ant-tasks
> ----------------------------------------------------
>
> Key: CASSANDRA-16391
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16391
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies
> Reporter: Michael Semb Wever
> Priority: High
> Labels: gsoc2021, lhf, mentor
>
> Cassandra resolves dependencies and generates maven pom files through the use of [maven-ant-tasks|http://maven.apache.org/ant-tasks/]. This is no longer a supported project.
> The recommended upgrade is to [resolver-ant-tasks|http://maven.apache.org/resolver-ant-tasks/]. It follows similar APIs so shouldn't be too impactful a change.
> The existing maven-ant-tasks has caused [some headaches already|https://issues.apache.org/jira/browse/CASSANDRA-16359] with internal super poms referencing insecure http:// central maven repository URLs that are no longer supported.
> We should also take the opportunity to
> - define the "test" scope (classpath) for those dependencies only used for tests (currently we are packaging test dependencies into the release binary artefact),
> - remove the jar files stored in the git repo under the "lib/" folder.
> These two above points have to happen in tandem, as the jar files under {{lib/}} are those that get bundled into the {{build/dist/lib/}} and hence the binary artefact. That is, all jar files under {{lib/}} are the project's "compile" scope, and all other dependencies defined in build.xml are either "provided" or "test" scope. These different scopes for dependencies are currently configured in different maven-ant-tasks poms. See https://github.com/apache/cassandra/commit/d43b9ce5092f8879a1a66afebab74d86e9e127fb#r45659668
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org