By bad, there is one reference in the Oozie pom.xml to Cloudera's Maven repo. This is is required to host a doxia twiki plugin modified by Oozie with extensions to handle Oozie documentation generation. This was discussed and accepted by the Apache Oozie developers.
Thanks. On Wed, Jan 29, 2014 at 9:24 PM, Alejandro Abdelnur <t...@cloudera.com>wrote: > > On Wed, Jan 29, 2014 at 5:38 PM, Suresh Srinivas > <sur...@hortonworks.com>wrote: > >> Have you >> looked at Oozie and are you going to open a jira to change that as well? >> > > Excuse me, what are we taking about here? > > The only references to Cloudera in Oozie source are in the Apache Oozie > site branch (https://svn.apache.org/repos/asf/oozie/site/trunk), next to > the committers/PMCs which are Cloudera employees. The same applies for the > the other committers/PMCs where their corresponding affiliation is being > shown. > > If you are referring to the Oozie logo colors, my answer to that is you > couldn't be more wrong, the Oozie logo was designed by a Yahoo employee > (which was not involved in Oozie development) before Oozie was open > sourced. > > Regarding the building of release tarballs. Tomorrow I'll spend some time > creating a Apache Jenkins job to help us doing that. That should settle > that issue without forcing any of us to buy a personal machine for this > task. Once I have something running I'll let folks now. > > Cheers. > > > > > > -- > Alejandro > -- Alejandro
