[
https://issues.apache.org/jira/browse/OOZIE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532110#comment-14532110
]
Shwetha G S commented on OOZIE-2229:
------------------------------------
We can change to classifier, it makes sense.
The problem is we need to define 3 modules for each hadoop major version and
all these modules can't have the same version 4.2.0-SNAPSHOT. I had tried this,
doesn't work
Or we can define just one module and include different sources depending on the
profile. This might work
> 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
>
>
> 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)
