it's the slf4j-log4j dependency (which transitively pulls in log4j) that
should either be removed from thrift's pom or marked with scope provided.
best is to remove it.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct res
I gave myself a ticket for that and will remove the left over log4j dependency
- Jake
On Apr 25, 2011, at 6:16 PM, Stephen Connolly wrote:
> No it means that the pom needs to have exclusions applied.
>
> going forward the thrift pom should be fixed to not have a transitive
> dep on the slf4j-lo
No it means that the pom needs to have exclusions applied.
going forward the thrift pom should be fixed to not have a transitive
dep on the slf4j-log4j implementation... the whole point of slf4j is
that the ned user picks the impl and the libraries along the way just
dep on the api.
-Stephen
On
Does this mean 0.6.1 isn't going to work for 0.8 maven deps?
I need to know because I'll upgrade the version in the source if we are
going to depend on it.
-Jake
On Mon, Apr 25, 2011 at 2:39 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> yep will be so doing, but those poms ha
yep will be so doing, but those poms have issues, such as depending
transitively on a slf4j implementation
also ranges are non reproducable, so it will be a specific version
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a dire
Stephen
As part of the 0.6.1 thrift release the libthrift and libfb303 are now
available in the apache repo
(http://repo1.maven.org/maven2/org/apache/thrift/). Can you reference these
jars rather than deploying a second set to the m2 repo in the cassandra deps
folder. I looked for a pom or ivy.
+1
On Fri, Apr 22, 2011 at 12:17 PM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 0.7.5.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-113/o
+1
On Fri, Apr 22, 2011 at 12:17 PM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 0.7.5.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-113/o
+1 nonbinding
On Apr 22, 2011, at 12:17 PM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 0.7.5.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassand
On Mon, Apr 25, 2011 at 12:53 PM, Jonathan Ellis wrote:
> Back when I used to run postgresql, I saw the same cycle:
>
> - most people don't bother testing until "stable" .0 is released
> - consequently, most people don't deploy to production until .1 is released
>
> I think moving the stable lab
Back when I used to run postgresql, I saw the same cycle:
- most people don't bother testing until "stable" .0 is released
- consequently, most people don't deploy to production until .1 is released
I think moving the stable label would be futile since the majority
will just wait that much long
It's not crazy, but the implementation would be a little involved (see
Brandon's comments to
https://issues.apache.org/jira/browse/CASSANDRA-1108).
On Sat, Apr 23, 2011 at 9:41 PM, Chris Burroughs
wrote:
> I wanted to see if this was generally useful before I just made a ticket.
>
> The scenario
As 0.8 approaches final status in the next few weeks, I wondered about how
releases receive the label, "current stable". I don't know if there's any
precedent for this, but I thought it might be nice to do a separate vote when
new major releases are out and weigh heavily those in the community
13 matches
Mail list logo
