[
https://issues.apache.org/jira/browse/OOZIE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199530#comment-13199530
]
[email protected] commented on OOZIE-667:
-----------------------------------------------------
bq. On 2012-02-03 03:11:48, Mohammad Islam wrote:
bq. > trunk/pom.xml, line 137
bq. > <https://reviews.apache.org/r/3726/diff/3/?file=72016#file72016line137>
bq. >
bq. > why do we need it?
we don't. removing.
- Alejandro
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3726/#review4786
-----------------------------------------------------------
On 2012-02-02 22:37:20, Alejandro Abdelnur wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/3726/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-02-02 22:37:20)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. The current mechanism allow to easily package/use new versions of hadoop
without complicating Oozie's POMs.
bq.
bq. mr1 & mr2 profiles are gone from oozie, now it refers to one of the
versions in hadooplibs.
bq.
bq. New maven modules under hadooplib define the hadoop-client/hadoop-test
POMs for different hadoop versions.
bq.
bq. Note that because of HADOOP-8009, hadoop will start providing a
hadoop-client artifact (even for already released versions), still we'll need
the corresponding hadooplibs module to be able to use the assembly (as it is
done as part of this patch) to pull into the oozie distro the JARs for the
supported/tested versions of Hadoop required for the client side.
bq.
bq. Note that this can be used tosimplify the logic of addtowar.sh that won't
have to be aware of the JARs deps of different versions of Hadoop or of hadoop
JARs at all.
bq.
bq.
bq. This addresses bug OOZIE-667.
bq. https://issues.apache.org/jira/browse/OOZIE-667
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. trunk/core/pom.xml 1239887
bq. trunk/core/src/test/java/org/apache/oozie/test/XTestCase.java 1239887
bq. trunk/docs/src/site/twiki/AG_Install.twiki 1239887
bq. trunk/docs/src/site/twiki/DG_QuickStart.twiki 1239887
bq. trunk/examples/pom.xml 1239887
bq. trunk/hadooplibs/hadoop-0_23_1/pom.xml PRE-CREATION
bq. trunk/hadooplibs/hadoop-0_24_0/pom.xml PRE-CREATION
bq. trunk/hadooplibs/hadoop-1_0_0/pom.xml PRE-CREATION
bq. trunk/hadooplibs/hadoop-test-0_23_1/pom.xml PRE-CREATION
bq. trunk/hadooplibs/hadoop-test-0_24_0/pom.xml PRE-CREATION
bq. trunk/hadooplibs/hadoop-test-1_0_0/pom.xml PRE-CREATION
bq. trunk/hadooplibs/pom.xml PRE-CREATION
bq. trunk/pom.xml 1239887
bq. trunk/sharelib/pom.xml 1239887
bq. trunk/sharelib/streaming/pom.xml 1239887
bq. trunk/src/main/assemblies/hadooplib.xml PRE-CREATION
bq. trunk/src/main/assemblies/hadooplibs.xml PRE-CREATION
bq. trunk/src/main/assemblies/partial-sharelib.xml 1239887
bq. trunk/webapp/pom.xml 1239887
bq.
bq. Diff: https://reviews.apache.org/r/3726/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Tested with 1.0.0 and 0.24.0-SNAPSHOTs (several testcases failures here
but that is still work in progress for the mr2 integration)
bq.
bq.
bq. Thanks,
bq.
bq. Alejandro
bq.
bq.
> Change the way Oozie brings in Hadoop JARs into the build
> ---------------------------------------------------------
>
> Key: OOZIE-667
> URL: https://issues.apache.org/jira/browse/OOZIE-667
> Project: Oozie
> Issue Type: Improvement
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> Currently we are using profiles with several exclussions and they are through
> out the POMs.
> A cleaner way, similar to sharelibs, is to have hadooplibs where there is a
> lib per version of Hadoop.
> Each Hadooplib would have the correct JARs for that version. These hadooplibs
> would be bundled with the release. Then it would be much easier for
> oozie-setup.sh just to point at the hadoplib dir required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
