[
https://issues.apache.org/jira/browse/MINVOKER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457682#comment-17457682
]
Slawomir Jaranowski edited comment on MINVOKER-294 at 12/11/21, 4:53 PM:
-------------------------------------------------------------------------
Currently we have the same option on global level:
{quote}
mavenExecutable can either be a file relative to ${maven.home}/bin/ or an
absolute file.
{quote}
Probably I need to support relative file also.
But this it will be in {{maven-invoker}}, I will create next issue for it after
checking.
was (Author: slawekjaranowski):
Currently we have the same option on global level:
{quote}
mavenExecutable can either be a file relative to ${maven.home}/bin/ or an
absolute file.
{quote}
Probably I need to support relative file also.
But this it will be in {{maven-invoker}}, I will create next issue for it after
checking.
> Allow override mavenExecutable in invoker.properties
> ----------------------------------------------------
>
> Key: MINVOKER-294
> URL: https://issues.apache.org/jira/browse/MINVOKER-294
> Project: Maven Invoker Plugin
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Priority: Major
>
> In some case of tests we want to change {{mavenExecutable}} for specific
> project or event for specific goal.
> Example usage:
> {code}
> invoker.goals.1 = wrapper:wrapper
> invoker.goals.2 = verify
> invoker.mavenExecutable.2 = ./mvnw
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
