[
https://issues.apache.org/jira/browse/OOZIE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546681#comment-14546681
]
Shwetha G S commented on OOZIE-2229:
------------------------------------
This will not cause profile issue. Profile is used to build the module and it
will have just one version and classifier always and the module builds fine.
The issue is with profile and transitive dependencies.
But it won't work with published jars though. I can't think of any other way
> oozie-hadoop-utils version does not conform to standard
> -------------------------------------------------------
>
> Key: OOZIE-2229
> URL: https://issues.apache.org/jira/browse/OOZIE-2229
> Project: Oozie
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Ryota Egashira
> Fix For: trunk
>
> Attachments: OOZIE-2229-v2.patch
>
>
> The version for oozie-hadoop-utils package for different versions is of the
> form
> <oozie.hadoop-utils.version>hadoop-${hadoop.majorversion}-${project.version}</oozie.hadoop-utils.version>
> i.e
> <version>hadoop-1-4.2.0-SNAPSHOT</version>
> <version>hadoop-2-4.2.0-SNAPSHOT</version>
> <version>hadoop-3-4.2.0-SNAPSHOT</version>
> This is breaking the standard major.minor.revision.patch versioning for jar
> or the <major version>.<minor version>.<incremental version>-<qualifier>
> standard for maven.
> This causes problems with maven plugins like versions and also problems with
> some of our internal systems which do not expect alphabets and special
> characters (- in this case) in the major version.
> The correct way to do this would be to use classifiers like how it is done in
> Pig and Sqoop for different versions of hadoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
