[
https://issues.apache.org/jira/browse/OOZIE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481924#comment-13481924
]
Alejandro Abdelnur commented on OOZIE-856:
------------------------------------------
Are you planning to do a 3.1.x-incubating release to include this fix?
If so, no need to create jira for the backport, if the release manager for the
branch (Mohammad in this case) is OK, just do the backport and change the fix
version in OOZIE-810. You'll also have to tweak the release-log.txt in trunk
and branch-3.3 to reflect that OOZIE-810 is part of 3.1.x release.
Also, just noticed that OOZIE-810 has not been marked as fixed and closed in
3.2.0, doing that.
> Backport OOZIE-810 to branch 3.1.3-incubating
> ---------------------------------------------
>
> Key: OOZIE-856
> URL: https://issues.apache.org/jira/browse/OOZIE-856
> Project: Oozie
> Issue Type: Bug
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Priority: Minor
>
> Oozie 3.1.3-incubating build fails with error
> Could not find artifact org.apache.maven.doxia:doxia-core:jar:1.0-alpha-9.2y
> in internal.maven.repo
> OOZIE-810 fixes this but it has not been backported to branch 3.1.3-incubating
--
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
