[jira] [Commented] (OOZIE-3306) Make it possible to override maven dependency plugin version number

["Andras Salamon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547500#comment-16547500 ] 

Andras Salamon commented on OOZIE-3306:
---------------------------------------

I've created a patch which makes it possible to specify the maven dependency plugin version using -Dmaven-dependency-plugin.version=2.10 . For grind it is possible to set it using GRIND_MAVEN_FLAGS:

{noformat}
export GRIND_MAVEN_FLAGS=-Dmaven-dependency-plugin.version=2.10
{noformat}

> Make it possible to override maven dependency plugin version number
> -------------------------------------------------------------------
>
>                 Key: OOZIE-3306
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3306
>             Project: Oozie
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 5.1.0
>         Environment: Mac OS X
> Java 8 u171
>            Reporter: Andras Salamon
>            Assignee: Andras Salamon
>            Priority: Minor
>         Attachments: OOZIE-3306-1.patch
>
>
> I wanted to speed up unit testing using [dist_test|https://github.com/cloudera/dist_test] framework and [grind|https://github.com/cloudera/dist_test/blob/master/docs/grind.md] frontend, and it does not work correctly with the hardwired maven dependency plugin version 3.0.2:
> {noformat}
> ...
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.0.2:copy-dependencies (default-cli) on project oozie-fluent-job-api: Some problems were encountered while processing the POMs:
> [ERROR] [ERROR] 'distributionManagement.status' must not be specified. @ line 39, column 13: 1 problem was encountered while building the effective model for xml-apis:xml-apis-ext:1.3.04
> [ERROR] [ERROR] 'distributionManagement.status' must not be specified. @ line 39, column 13
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :oozie-fluent-job-api
> ...
> {noformat}
> Downgrading to version 2.10 solves the problem but it requires manually modify the version number in pom.xml file:
> {noformat}
> <plugin>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-dependency-plugin</artifactId>
>     <version>2.10</version>
> </plugin>
> {noformat}
> It would be great to be able to customize the version number without modifying the pom.xml file.



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