Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka, mail # dev - remaining jars in svn (was Fwd: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2))


Copy link to this message
-
Re: remaining jars in svn (was Fwd: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2))
Joe Stein 2012-06-19, 05:22
if the jars that are left are still an issue

find ./branches/0.7.1/ -name *jar
./branches/0.7.1//contrib/hadoop-consumer/lib/pig-0.8.0-core.jar
./branches/0.7.1//contrib/hadoop-consumer/lib/piggybank.jar
./branches/0.7.1//contrib/hadoop-producer/lib/pig-0.8.0-core.jar
./branches/0.7.1//contrib/hadoop-producer/lib/piggybank.jar
./branches/0.7.1//lib/sbt-launch.jar

pig-0.8.0-core.jar is in maven

piggybank is not maven

sbt-launch.jar we either have to leave in (since we have such an older
version) or proceed with https://issues.apache.org/jira/browse/KAFKA-134 so
we can point people to the "latest" sbt since this is what we need to get
things rolling

and then there is the nunit dll

not sure if all or none are an issue or if the goal here is just to move
ping-0.8.0-core.jar out and into maven? want to keep this discussion moving
so we can come to an agreement for RC3

On Mon, Jun 18, 2012 at 10:47 PM, Chris Burroughs <[EMAIL PROTECTED]
> wrote:

> My interpretation of the long "Binary dependencies in source releases"
> thread is that the build tools are (I think) defensible, but it really
> would be best if we could get rid of the rest.
>
> I see that Neha and Jacob already did most of the work last round in
> KAFKA-222 (go team!).  In the comments pig is called out as a problem,
> but it looks like this is taken care of in PIG-1334.  Any reason we
> can't mavenize those as well?
>
> I'm not sure what to do with DLLs.
>
>
>
> -------- Original Message --------
> Subject: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)
> Date: Mon, 18 Jun 2012 21:34:41 -0400
> From: Joe Stein <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED]
>
> I uploaded a md5 checksum
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ to
> go along with the detached signature that was generated already
>
> starting the kafka server is in the quick start
> http://incubator.apache.org/kafka/quickstart.html
>
> looking at Cassandra and Hadoop source distributions both have jars in them
> too, so not sure the issue you are raising others might have a better
> understanding or I am missing something you are trying to point out
>
> I would like to keep the RC2 voting open for another few days to see if
> this release passes (as folks have not had time to review) or we can get to
> what issues we need to have resolved that can be done for RC3 for a new
> vote either with objective to getting 0.7.1 released.
>
> current votes:
>
> +1 [1] +0 [0] -1 [0] from the PPMC
>
> and
>
> +1 [0] +0 [0] -1 [0] from the IPMC
>
> please let me know if there is something different we want or should have
> been doing here or that I can be or should be doing differently.
>
> thanks!
>
> On Mon, Jun 18, 2012 at 4:53 PM, Kevan Miller <[EMAIL PROTECTED]
> >wrote:
>
> > Things that I've noted:
> >
> > I don't see a checksum for your release in
> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/--
> > your release manager will need to generate a checksum for the release.
> >
> > It would be nice if your archive extracted into an
> > apache-kafka-0.7.1-incubating directory (or similar name rather than .),
> > but that's minor.
> >
> > I see the following binary files in your source distribution:
> >
> > ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll
> > ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar
> > ./contrib/hadoop-consumer/lib/piggybank.jar
> > ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar
> > ./contrib/hadoop-producer/lib/piggybank.jar
> > ./lib/sbt-launch.jar
> >
> > If I understand correctly, this does not meet a definition of an open
> > source release (which is what an apache release is…). It looks like this
> is
> > how your last release was packaged, also… I don't know if this is a
> > blocking issue (for an incubator release), but I think you need to work
> on
> > resolving this (i.e. remove binaries from your source)…

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/