[GitHub] [maven-mvnd] gnodet commented on issue #787: mvnd overwrites PATH for vanilla mvn

["gnodet (via GitHub)" <gi...@apache.org>]

gnodet commented on issue #787:
URL: https://github.com/apache/maven-mvnd/issues/787#issuecomment-1462209248

   > @gnodet I'd prefer it if we do not follow this approach on SDKMAN. Having multiple packages for mvnd will be confusing for our users.
   > 
   > I'd like us to keep things as they are (one native package per version per platform). I also do not want the mvnd package to clobber the Maven binary.
   
   @marc0der So the next `mvnd` release will support both maven 3.9.x and 4.0.x, but it will provide 2 different distributions for each platform (not a single distribution supporting two different maven versions).  The reason is that most of the code is common, so it's easier to maintain two distributions from a single source tree, rather than having to port any change to 2 different branches. See https://github.com/apache/maven-mvnd/actions/runs/4374385157.
   I suppose those will have to be published as `mvnd` version = `1.0.0-m5-m39` and `1.0.0-m5-m40`
   
   Was your objection was related the above point ? Else is there another way that `mvnd` publish a distribution for non natively supported platforms ?  Reading the doc, I would think publishing a `UNIVERSAL` flavour would work, but you'll know better...
   
   On the `mvnd` / `mvn` binaries mix, I'll revert the change that mixes up `mvnd` and `mvn` binaries, though I may come back to it in a few months when things have matured a bit more.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org