I had the same problem...export PATH=$PATH: && mvn
clean test solved my problem
On Wednesday, April 29, 2015 at 12:55:21 AM UTC+5:30, Erick Macedo wrote:
>
> Hi,
>
> I'm using the plugin Publish over SSH to run a remote command maven on a
> linux machine with properly configured maven.
>
>
If you expect your command to have these values set from .bashrc: .bashrc is
only loaded for interactive shells, which the Publish over SSH plugin likely is
not. Find another way to define these, or explicitly load (source) .bashrc.
'man bash', section 'invocation'
On 28.04.2015, at 23:16,
I can not understand this behavior.
In Exec command: cd test / build-38 / project ls echo $ M2 mvn -v
This command does the following:
1 - cd test / build-38 / project (in this directory on the remote server)
2 - ls (list the remote server content)
3 - echo $ M2 (Prints $ M2 LOCAL server,
It works as the user that you are connecting as? Is there anything in the
.bashrc that would set the path to mvn? Perhaps the Publish Over SSH
doesn't run in such a way that the .bashrc file is loaded? Check into these
things.
On Tue, Apr 28, 2015 at 1:19 PM Erick Macedo erickfmac...@gmail.com
Hi,
I'm using the plugin Publish over SSH to run a remote command maven on a
linux machine with properly configured maven.
However when running mvn command is generated an error bash: mvn: command
not found.
The plugin is properly connecting the remote machine, as for testing in the
Exec
