Hi Mohammad,

Thanks for the reply.

As it appears, the
repository<http://mirrors.ukfast.co.uk/sites/ftp.apache.org/oozie/3.2.0-incubating/>no
longer contains binary tar files, so one has to build them from
source.
The Distribution
Contents<http://oozie.apache.org/docs/3.2.0-incubating/index.html#Distribution_Contents>section
seems to be out of date.

For the record, I followed these steps:

   1. Installing/updating the system dependencies as per the Build System
   Requirements described
here<http://oozie.apache.org/docs/3.2.0-incubating/ENG_Building.html#System_Requirements>
   ;
   2. Execute bin/mkdistro.sh
   3. Retrieve the client .jar from
   
oozie-3.2.0-incubating/distro/target/oozie-3.2.0-incubating-distro/oozie-3.2.0-incubating/lib/oozie-client-3.2.0-incubating.jar

Perhaps it helps someone else in the future.


Regards,
Attila




On 17 November 2012 07:16, Mohammad Islam <[email protected]> wrote:

> Hi Attila,
> Under the large tar file, there should be client tar file (such
> as oozie-client-3.2.0-incubating.tar.gz). you can find the lib directory in
> that tar.
>
> I'm not sure the tar file that you mentioned, is  a binary one or the src
> one. If it is src one, you will need to build the tar file which could be
> found under distro/target directory.
>
> If you can't find it, please let us know with more details.
>
> Regards,
> Mohammad
>
>
> ________________________________
>  From: Attila Szász <[email protected]>
> To: [email protected]
> Sent: Friday, November 16, 2012 11:11 AM
> Subject: Oozie 3.2.0 distro and binaries
>
> Hi,
>
> I'm newby to Oozie and I would like to use the client Java API.
> The distribution contents
> description<
> http://oozie.apache.org/docs/3.2.0-incubating/index.html#Distribution_Contents
> >hints
> that there is supposed to be a lib folder with client JAR files
> within the 3.2.0
> distro<
> http://mirrors.ukfast.co.uk/sites/ftp.apache.org/oozie/3.2.0-incubating/oozie-3.2.0-incubating.tar.gz
> >but
> I cannot see it.
> Am I missing something?
>
> Thanks.
> Attila
>

Reply via email to