Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invoker plugin fails cause mvn command is not available #35

Open
rmannibucau opened this issue Jul 12, 2018 · 2 comments
Open

Invoker plugin fails cause mvn command is not available #35

rmannibucau opened this issue Jul 12, 2018 · 2 comments

Comments

@rmannibucau
Copy link

rmannibucau commented Jul 12, 2018

Reason: Maven executable not found at: /home/rmannibucau/softwares/mvnsh-1.2.0-SNAPSHOT/bin/mvn

to solve that, mvnsh could add a mvn script (should be easy) in bin/? Alternative is to make invoker plugin supporting another maven home transparently but it requires a built in extension which is a bit more fragile (setting mavenExecutable using M2_HOME probably)

Workaround:

<profile>
  <id>mvnsh</id>
  <activation>
    <file>
      <exists>${maven.home}/bin/mvnsh</exists>
    </file>
  </activation>
  <properties>
    <maven.executable.location>${maven.home}/bin/mvnx</maven.executable.location>
  </properties>
</profile>

and in maven-invoker-plugin:

<mavenExecutable>${maven.executable.location}</mavenExecutable>

@jdillon
Copy link
Owner

jdillon commented Jul 16, 2018

what are you running that produces "Maven executable not found" ?

@rmannibucau
Copy link
Author

Plain mvn install with invoker 3.0.x. i'm trying to build http://github.com/talend/component-runtime but i get several small issues with mvnsh compared to native mvn. It is in component-runtime-beam or the maven plugin one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants