ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alok Lal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-825) groupId of all ranger pom's should be consistent and follow convention.
Date Tue, 26 Jan 2016 21:24:39 GMT

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

Alok Lal updated RANGER-825:
----------------------------
    Description: 
# Some of ranger jars are published with a groupId that is not along the recommended [naming
convention|https://maven.apache.org/guides/mini/guide-naming-conventions.html].
# Children specify their version.  In Ranger it would be unusual for us to release items at
different versions.  So it is best to inherit parent's version and avoid duplication.


  was:Ideally child pom's should inherit the groupId and version of their parent.


> groupId of all ranger pom's should be consistent and follow convention.
> -----------------------------------------------------------------------
>
>                 Key: RANGER-825
>                 URL: https://issues.apache.org/jira/browse/RANGER-825
>             Project: Ranger
>          Issue Type: Bug
>          Components: build-infra
>    Affects Versions: 0.5.1
>            Reporter: Alok Lal
>            Assignee: Alok Lal
>
> # Some of ranger jars are published with a groupId that is not along the recommended
[naming convention|https://maven.apache.org/guides/mini/guide-naming-conventions.html].
> # Children specify their version.  In Ranger it would be unusual for us to release items
at different versions.  So it is best to inherit parent's version and avoid duplication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message