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

Ignite TC Bot commented on IGNITE-15872:
----------------------------------------

{panel:title=Branch: [pull/9554/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9554/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6256340&buildTypeId=IgniteTests24Java8_RunAll]

> Add Maven Wrapper to facilitate and standardize the build process
> -----------------------------------------------------------------
>
>                 Key: IGNITE-15872
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15872
>             Project: Ignite
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.13
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, one builds Ignite using mvn command directly. This requires Maven 
> to be installed, present on the PATH, and each user may have their own Maven 
> version.
> Maven Wrapper will allow to achieve the following:
>  # Build Ignite easier (i.e., on machines where Maven is not installed yet)
>  # Use a standard version of Maven (which should decrease possibility for 
> builds producing different results due to different Maven versions; for 
> example, in one Maven version the build works ok, but in another it fails)
> This change should not break anything as the old way to build using mvn 
> command directly still remains possible.
> According to 
> [https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt] , Maven 
> Wrapper is licensed under Apache 2 license, so no license issues should arise.
> On the 'CI build' side, Maven Wrapper caches Maven under $HOME/.m2/wrapper/ , 
> so, if the whole $HOME/.m2/ directory is reused, no additional problems with 
> 'downloading Maven each build' should emerge.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to