cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Byström (JIRA) <>
Subject [jira] Updated: (CASSANDRA-301) Support a maven release
Date Tue, 21 Jul 2009 20:53:14 GMT


Carl Byström updated CASSANDRA-301:

    Attachment: CASSANDRA-301_v6.diff

Added an updated POM based on Michael's version. Managed to find the Groovy and google-collection
deps in an official repo.

There are still problems with the dependencies. Some deps (clhm, high-scale-lib, libthrift,
commons-javaflow) don't exist in official repos.
I guess Hiram added these as "system" deps because they couldn't be found elsewhere. But this
creates a problem where the generated artifacts expects to find these deps on the end-users
computer (that's what the <scope>-tag says with "system"). Normally, Maven would go
look in it's repos for the missing artifact and resolve it.

With Cassandra being something that people will include as a dependency, they expect the everything
to resolve. Listing deps as "system" is usually only done with deps having special licenses
that forbid them to be distributed by normal Maven repos.

The way I see it, following options exist:
A) Convince the developers of these libraries to put the right version in an official repo.
B) Package the library ourselves and submit to an official repo.
C) Package the library ourselves but add it to the Apache repo along with Cassandra.
D) Package the library ourselves and host it in a 3rd party repository (forcing users of the
cassandra dep to add this repo to their repo list)

Unfortunately, the only viable solutions is A. (Perhaps B, not sure if a random person can
submit deps to the official repos)
Without these missing deps readily available to Maven users of Cassandra, things will not
work (unless they of course manually import these "system" deps by hand).

Perhaps there are ways around this with Maven, I don't know. Been using it for a couple of
years but only for internal projects where we maintain our own private repo.

> Support a maven release
> -----------------------
>                 Key: CASSANDRA-301
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Hiram Chirino
>         Attachments: CASSANDRA-301.patch.4, CASSANDRA-301_v5.diff, CASSANDRA-301_v6.diff

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message