[
https://issues.apache.org/jira/browse/OOZIE-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636554#comment-13636554
]
Alejandro Abdelnur commented on OOZIE-1334:
-------------------------------------------
Renata, we did something like that at the very beginning, but it does not work.
You can not put variables in the POM versions that are resolved from the parent
POM version. These POMs are unusable when deployed in a maven repo.
We need to add, in oozie hadooplibs/ the corresponding module for every version
of hadoop we want to provide easy config.
Please close this JIRA as won't fix.
> Make property hadoop.version valid for all Oozie hadoop related poms
> --------------------------------------------------------------------
>
> Key: OOZIE-1334
> URL: https://issues.apache.org/jira/browse/OOZIE-1334
> Project: Oozie
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.3.0
> Environment: x86 Java 6
> Reporter: Renata Ghisloti Duarte de Souza
> Priority: Minor
> Fix For: 3.3.0
>
> Attachments: OOZIE-1334.patch
>
>
> Today it is not possible to build oozie using the command "mvn clean compile
> -Dhadoop.version=1.1.2". pom files from directory hadooplibs have to me
> changed manually
> to match the Hadoop Version.
> This patch proposes a modification so that "mvn clean compile
> -Dhadoop.version=1.1.2" command runs successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
