+1
...ant
On Wed, Mar 17, 2010 at 7:17 PM, Eric Evans wrote:
>
> It's been a bit since the last beta, and while many important fixes have
> made their way in[1], we're still not quite ready to roll a release
> candidate. I propose one more beta in order to get some of this new work
> tested w
As one of the committers to cassandra.gem, microseconds is the way to
go. Specificity is nice to have when you haven't been thinking about
timestamps and suddenly have a deep, abiding need to care about them.
I cannot understate that. It is much easier to remove the specificity
than it is to put i
A standard default would be nice, but while we're making
recommendations I'd also suggest that client libs should make this
parameter easy to override. Client apps can do lots of interesting
things by setting timestamps explicitly. You can get a sort of quasi-
transaction by using the same t
+1 I think this is a great idea. I've been bitten by this when switching
clients, and it took a while to figure out what was going on. Good job on
pycassa, vomjom!
-Ben
2010/3/18 Ted Zlatanov
> On Thu, 18 Mar 2010 02:36:35 -0500 Jonathan Hseu
> wrote:
>
> JH> Jonathan Ellis suggested that I
> This is not an issue of whether or not we can distribute these jars, (we
> can). It boils down to the _requirements_ of distributing them, i.e. the
> inclusion of license text and attribution notices as required.
>
> So long as we are properly documenting license and attribution, we can
> check a
On Thu, 2010-03-18 at 10:15 -0600, Jesse McConnell wrote:
> > The binary release artifacts created by the `release' target in
> > build.xml, (they look something like
> > apache-cassandra-$VERSION-bin.tar.gz on the mirrors).
>
> actually I was asking about the problematic artifacts inside that
> d
> The binary release artifacts created by the `release' target in
> build.xml, (they look something like
> apache-cassandra-$VERSION-bin.tar.gz on the mirrors).
actually I was asking about the problematic artifacts inside that
distribution that were in question as to whether you could
redistribute
On Thu, 2010-03-18 at 09:28 -0600, Jesse McConnell wrote:
> >> +1 to have your official 'distribution' contain everything needed
> to
> >> run
> >
> > It remains to be seen whether this can legally be done.
>
> sorry, I didn't see which artifacts would be problematic for this,
> could you call the
>> +1 to have your official 'distribution' contain everything needed to
>> run
>
> It remains to be seen whether this can legally be done.
sorry, I didn't see which artifacts would be problematic for this,
could you call them out?
apache legal has been very helpful on this in the past for maven,
On Thu, 2010-03-18 at 10:13 -0500, Jesse McConnell wrote:
> imo the 'distribution' you produce should come bundled with everything
> you need to run it, it is very awkward to drop the distro on a bare
> box and then have to install ant just to bootstrap that distribution
> into a usable state
No o
imo the 'distribution' you produce should come bundled with everything
you need to run it, it is very awkward to drop the distro on a bare
box and then have to install ant just to bootstrap that distribution
into a usable state
+1 to use ivy to not park jars in svn
+1 to have your official 'distr
On Wed, 2010-03-17 at 23:32 -0500, Paul Querna wrote:
> > Lack of java-devness showing: Can't the -bin tarball just include
> the
> > 'ivy-retrieve' step pre-done?
> >
> > At least then everyone will test the same -bin, significantly
> reducing
> > the lack of trusted path in problems 1 & 2.
> >
>
+1
Matthieu
On Wed, Mar 17, 2010 at 10:19 PM, Ian Holsman wrote:
> +1 [binding]
> On 3/18/10 7:13 AM, Jonathan Ellis wrote:
>
>> +1 [binding]
>>
>> On Wed, Mar 17, 2010 at 2:17 PM, Eric Evans wrote:
>>
>>
>>> It's been a bit since the last beta, and while many important fixes have
>>> made the
On Thu, 18 Mar 2010 02:36:35 -0500 Jonathan Hseu wrote:
JH> Jonathan Ellis suggested that I bring this issue to the dev mailing list:
JH> Cassandra should recommended a default timestamp across all clients
JH> libraries.
...
JH> Here's what different clients are using:
JH> 1. Cassandra CLI: Mil
Paul Querna wrote:
On Wed, Mar 17, 2010 at 4:21 PM, Eric Evans wrote:
During the 0.6 cycle Ivy was introduced to manage (most of) our
dependencies, and where possible, jars were removed from svn and no
longer included in binary release artifacts. Recently though this change
has been called into
Jonathan Ellis suggested that I bring this issue to the dev mailing list:
Cassandra should recommended a default timestamp across all clients
libraries.
Many users on IRC are having difficulty when using different clients because
different clients are using different timestamps. If you insert wi
16 matches
Mail list logo
