You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by Mohammad Islam <mi...@yahoo.com> on 2011/12/02 04:26:57 UTC

Too many projects in Oozie

Hi,
I can see there are many new sub-projects in Oozie when opened through Eclipse. The examples are sharelib-pig, sharelib-hive, sharelib-sqoop, sharelib-streaming. So for every type of action, we will add a new sharelib. 

Is it possible to design it differently  so that every product will not have a new projects. Instead, they will be in a common project called 'sharelib' which will contain all action specific stuffs.

Regards,
Mohammad

Re: Too many projects in Oozie

Posted by Alejandro Abdelnur <tu...@cloudera.com>.

Mohammad,

What you are suggesting is what it was before OOZIE-610. The problem is
that then it is not possible to use maven dependency/assembly for creating
the lib dirs for each action (with different versions of transitive
dependencies) and it would not be possible to have multiple libraries for a
single action (ie pig 0.8.0 & 0.9.0).

Note that the build time has not increased (or at most 1 or 2 seconds).

>From your IDE, you can just ignore those modules.

Thanks.

Alejandro

On Thu, Dec 1, 2011 at 7:26 PM, Mohammad Islam <mi...@yahoo.com> wrote:

> Hi,
> I can see there are many new sub-projects in Oozie when opened through
> Eclipse. The examples are sharelib-pig, sharelib-hive, sharelib-sqoop,
> sharelib-streaming. So for every type of action, we will add a new
> sharelib.
>
> Is it possible to design it differently  so that every product will not
> have a new projects. Instead, they will be in a common project called
> 'sharelib' which will contain all action specific stuffs.
>
> Regards,
> Mohammad