[
https://issues.apache.org/jira/browse/OOZIE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757561#comment-13757561
]
Alejandro Abdelnur edited comment on OOZIE-1490 at 9/4/13 8:37 AM:
-------------------------------------------------------------------
David, a POM with
<version>$\{hadoopOne.version\}.oozie-4.1.0-SNAPSHOT</version> is unusable when
deployed to a maven repo. we cannot do that. I know it works when you are
building locally, but the artifact cannot be used from a maven repo.
was (Author: tucu00):
David, a POM with
<version>${hadoopOne.version}.oozie-4.1.0-SNAPSHOT</version> is unusable when
deployed to a maven repo. we cannot do that. I know it works when you are
building locally, but the artifact cannot be used from a maven repo.
> Remove unix OS enforcement and parametrize hadoop versions
> ----------------------------------------------------------
>
> Key: OOZIE-1490
> URL: https://issues.apache.org/jira/browse/OOZIE-1490
> Project: Oozie
> Issue Type: Sub-task
> Components: build
> Environment: Windows
> Reporter: David Wannemacher
> Assignee: David Wannemacher
> Fix For: trunk
>
> Attachments: OOZIE-1490.2.patch, OOZIE-1490.patch
>
>
> Windows builds do not run because there is a requireOS restriction for unix.
> Also, building and running unit tests on windows requires that a specific
> hadoop version is used. Right now this requires editing multiple pom.xml
> files because the version is hard-coded. This should be fixed to allow
> passing specific hadoop versions to the build on the command-line.
--
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