You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Artem Ervits (JIRA)" <ji...@apache.org> on 2018/05/24 17:00:00 UTC

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

     [ https://issues.apache.org/jira/browse/OOZIE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Ervits updated OOZIE-2105:
--------------------------------
    Attachment: OOZIE-2105-02.patch

> Make version of submodules configurable with parent version 
> ------------------------------------------------------------
>
>                 Key: OOZIE-2105
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2105
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Mohammad Kamrul Islam
>            Assignee: Artem Ervits
>            Priority: Major
>         Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent version. If someone changes the parent version, all sub-modules versions will need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we use
> <groupId>org.apache.oozie</groupId>
>      <artifactId>oozie-hadoop</artifactId>
>      <version>1.1.1.oozie-4.1.0</version>
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use this :
> <version>1.1.1.oozie-${parent.version}</version>
>  
> This will allow to change only the parent version in root pom.xml.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)