You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2018/04/23 10:07:00 UTC

[jira] [Assigned] (ATLAS-2595) Improve version consistency in POMs (omas, omrs...)

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

Nigel Jones reassigned ATLAS-2595:
----------------------------------

    Assignee: Nigel Jones

> Improve version consistency in POMs (omas, omrs...)
> ---------------------------------------------------
>
>                 Key: ATLAS-2595
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2595
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>            Priority: Major
>
> In maven projects generally, the <PluginManagement> or <DependencyManagement> tags can be used to provide some generic attributes for plugins, versions of dependencies etc in a top level pom, and then child poms no longer need to specify, unless they wish to override.
> Some components in atlas take a different approach, by setting an explicit version in a property in the top level pom, and then using this variable in the child pom.
> The current omrs, omas poms tend to explicitly refer to version, which can lead to more inconsistency by mistake (they can override if essential for function), so this Jira is being opened to consolidate



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