I can take up publishing Oozie maven artifacts.
Tucu, does this require some special permissions? If yes, can you grant them to
me?
Mona Chitnis
Software Engineer, Hadoop Team
Yahoo!
On Monday, March 31, 2014 5:54 PM, Robert Kanter rkan...@cloudera.com wrote:
That would be fine, but we might
Hi Robert,
Thanks for the running the process!
Since we just voted for Oozie 4.0.1 source release, we can plan for the binary
release in a separate process.
Although ,I believe, Apache primarily needs the source release, but most of
the hadoop stack is also releasing the binary package. It
and we should get oozie jars in the maven repo
thx
Alejandro
(phone typing)
On Mar 31, 2014, at 11:23, Mohammad Islam misla...@yahoo.com wrote:
Hi Robert,
Thanks for the running the process!
Since we just voted for Oozie 4.0.1 source release, we can plan for the
binary release in a
That sounds like a good idea; users have been asking for binaries for a
long time. I suppose we'd have to make a binary release for each version
of Hadoop we're targeting? (i.e. Hadoop 1.1.1, Hadoop 2.3.0, Hadoop
0.23.5).
By the way, the 4.0.1 release is ready to go, I'm just waiting on the
doesn't the binary contain the hadooplib TARs? If so, one single binary
should be OK
thx
On Mon, Mar 31, 2014 at 12:42 PM, Robert Kanter rkan...@cloudera.comwrote:
That sounds like a good idea; users have been asking for binaries for a
long time. I suppose we'd have to make a binary release
That would be fine, but we might want to make the whole libext thing more
clear.
I can see a lot of users, under the assumption that the binary release
would be ready to go out of the box, skipping the step of untarring the
correct hadooplib tarball into the libext dir, or choosing the wrong one.
