[
https://issues.apache.org/jira/browse/IGNITE-23452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891512#comment-17891512
]
Ignite TC Bot commented on IGNITE-23452:
----------------------------------------
{panel:title=Branch: [pull/11603/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11603/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8120605&buildTypeId=IgniteTests24Java8_RunAll]
> ignite-compatibility module should use ./mvnw script
> ----------------------------------------------------
>
> Key: IGNITE-23452
> URL: https://issues.apache.org/jira/browse/IGNITE-23452
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maksim Timonin
> Assignee: Aleksandr Popov
> Priority: Major
> Labels: good-first-issue
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignite repo has ./mvnw script in root directory. Compatibility tests search
> for local 'mvn' but skip this script. It then requires user setup maven or
> M2_HOME dir for tests. That is inconvenient.
> Changes should be done in the method `MavenUtils#resolveMavenApplicationPath`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
