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

Do not require the mvn in PATH to come from mvnd dist #7

Closed
ppalaga opened this issue Oct 1, 2019 · 4 comments
Closed

Do not require the mvn in PATH to come from mvnd dist #7

ppalaga opened this issue Oct 1, 2019 · 4 comments
Labels
wontfix This will not be worked on

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Oct 1, 2019

To avoid some bugs in mvnd I'd like to use the stock Maven via mvn in my PATH.

ACTUAL:
Currently both mvnd and mvn in the PATH must point to the scripts from the mvnd distro for mvnd to work. If the mvn in my PATH points to the stock Maven then mvnd stops working.

If I use mvn from the mvnd distro it seems to behave like mvnd - which I assume does not help me to avoid the mvnd bugs.

EXPECTED:
It should be enough to have mvnd in the path for mvnd to work. mvn should stay pointing at the stock Maven.

@ppalaga
Copy link
Contributor Author

ppalaga commented Oct 1, 2019

Maybe mvnd should be able to pick its own mvn using MVND_HOME env var if MVND_HOME is set?

@tadayosi
Copy link
Member

tadayosi commented Oct 1, 2019

Currently, as a workaround I only ln -s $MVND_HOME/target/maven-distro/bin/mvnd . in ~/.local/bin and use mvnd only.

@ppalaga
Copy link
Contributor Author

ppalaga commented Oct 1, 2019

The only valid workaround I see is to alias the stock Maven as mvnn and leave mvn for the one from mvnd.

@gnodet
Copy link
Contributor

gnodet commented Oct 1, 2019

Right, I think it would make sense to use a MVND_HOME env variable instead, so that the stock mvn command is not disturbed.

@gnodet gnodet closed this as completed in 45a49ab Oct 1, 2019
ppalaga pushed a commit to ppalaga/mvnd that referenced this issue Jul 14, 2020
@ppalaga ppalaga added this to the Black hole milestone Jul 30, 2020
@gnodet gnodet added the wontfix This will not be worked on label Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants