cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13724) Cleanup build.xml dependencies
Date Wed, 26 Jul 2017 13:29:00 GMT


Stefan Podkowinski commented on CASSANDRA-13724:

The biggest benefit is that you're more open to community contributions with a maven based
build process. Our home-grown ant solution works, but most devs will only ever have to build,
test and manage dependencies. Standard tasks like this shouldn't require all the complexity
that comes with build.xml.

What I'd like to try out at some point is to see if we can have both solutions in the future,
the ant process working as is and additionally maven, which would be able to compile, test
and package the project. Ant targets could then be migrated to maven over time, or just [executed
by maven|].

It's really not that hard to do this step by step. I managed to replace the maven-ant-tasks
(project not maintained for many years) with the Aether dependency resolver that is used starting
in maven 3. Doing so allows you to externalize pom files with your dependencies and we could
continue to take this further by calling from ant into maven or the other way around (but
probably not in this ticket). See [WIP-13724|]

> Cleanup build.xml dependencies
> ------------------------------
>                 Key: CASSANDRA-13724
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Stefan Podkowinski
>            Priority: Minor
>             Fix For: 4.x
> As discussed in CASSANDRA-12996, the build.xml has become pretty messy and could use
some cleanup and additional inline comments. Maybe parts of it could be even split up or externalized.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message