mojohaus / mojohaus/exec-maven-plugin
Unable to run process which is not in same folder
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 191
- Forks
- 111
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 4
Description
I am trying to run gulp with my project on Jenkins machine. I want to avoid global installation and setting path. Though I give absolute path of gulp installation, it is not getting picked up. There should be some way to specify absolute path
Below is my configuration
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.4.0</version>
<executions>
<execution>
<id>exec-gulp</id>
<phase>prepare-package</phase>
<configuration>
<executable>/a/b/c/node_modules/.bin/gulp</executable>
<arguments>
<argument>--dir</argument>
<argument>${project.artifactId}-${project.version}</argument>
</arguments>
</configuration>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
</plugin>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the exec-maven-plugin's configuration and the exec goal, then reproduce the Jenkins invocation using the absolute path shown. Done means the configured absolute gulp path is accepted and the process runs with the supplied --dir arguments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100