incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hannes Schmidt <>
Subject Re: Thoughts on issue 697 (Mitigate unpublished dependencies when using Cassandra with Maven)
Date Sun, 11 Apr 2010 17:57:22 GMT
On Sat, Apr 10, 2010 at 4:50 PM, Tatu Saloranta <>wrote:

> On Sat, Apr 10, 2010 at 7:10 AM, Hannes Schmidt <>
> wrote:
> > On Fri, Apr 9, 2010 at 12:24 PM, Gary Dusbabek <>
> wrote:
> ...
> >> Why?  "To make things easier for mvn users" isn't enough of an
> >> argument to convince me.
> >>
> >
> > I can't really help you with that. Maven users make up a considerable
> > segment of your potential user base. If making life easier for them
> doesn't
> > motivate you, I am not sure what does. It surely isn't a sense for the
> > community.
> How about stopping asking for others do the work, and doing it
> yourself, if YOU care so much?
> This approach (of actually DOING something) has been suggested
> multiple times: and next comments is likely to be along lines of "just
> fuck off".

Tatu, I can't do the work. If I could, I already would have done it. And
it's not because I don't have the time. Only the project owners can deploy
the jars to a public Maven repository. This is minimal amount of work that
would be necessary simply to save the work another contributor had already

I made the mistake of mingling two issues: A) moving the build for the trunk
to Maven (which is clearly not going to happen) and B) saving the efforts
that went into the Maven POM which was contributed for 0.5. The latter
should have been the primary focus of the discussion and I am responsible
for distracting from it.

> And please do not talk as if you represented significant segment of
> unhappy users -- if there are others, they are quite capable of
> speaking up to support your request.

Given the hostility of your response they might be afraid to speak up? But
seriously, most of them probably don't have the time to research this
problem or "whine" in here. They just deploy the respective artifacts to
their local repo and get on with life which is probably what I should have
done in the first place. Unfortunately, this would only work for 0.5,
though, not for the trunk because the POM there is not functional. This is
where A) comes in and I do realize that I should be the one to fix the POM
and ask for the artifacts to be deployed. But this is exactly the same kind
of work that went into the 0.5 POM. And did the committers live up to their

Assuming that the team does not want to move to Maven, there are two
alternatives to A): Either the Ant/Ivy build could deploy the artifacts to a
Maven repository or someone could generate stub POMs for Cassandra. I don't
think stubs are gonna make it into a public repo so these would have to be
published somewhere else.

> Pardon my french, but this seems to fall to the repugnant category of
> "not enough time to help, enough time to whine".

Hmm, yeah, I really don't appreciate your tone.

> -+ Tatu +-
> ps. I'm not part of project team, and above opinion is my personal
> one. Just so there's no misunderstanding.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message