[
https://issues.apache.org/jira/browse/MSHARED-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492935#comment-17492935
]
Hudson commented on MSHARED-1009:
---------------------------------
Build succeeded in Jenkins: Maven » The Apache Software Foundation »
maven-invoker » master #3
See
https://ci-maven.apache.org/job/Maven/job/maven-github/job/maven-invoker/job/master/3/
> Allow providing Maven executable from workspace
> -----------------------------------------------
>
> Key: MSHARED-1009
> URL: https://issues.apache.org/jira/browse/MSHARED-1009
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-invoker
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: maven-invoker-3.2.0
>
>
> Currently provided Maven executable is searched in Maven home location and
> absolute path is used from Maven distribution.
> Maven project can use {{wrapper}} and Maven executable, like {{mvnw}}, exists
> in project workspace.
> Firs project workspace should be checked, if provide executable exists in
> project should be used as relative path.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
