[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-27 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980641749


   but for sure, there is the question: what should be the default? current 
`script`or `bin` as it was in Takari?
   I kept the `script` default value that Robert chose previously, changing is 
easy, it's really just a choice to do


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-27 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980639933


   the issue you have is only with SNAPSHOTs of maven-wrapper, that are 
obviously not published to central
   But with releases, there won't be any problem for normal users using default
   
   during development with SNAPSHOT maven-wrapper, see last section of 
https://maven.apache.org/wrapper-archives/wrapper-LATEST/


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-27 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980543639


   last try:
   - code = https://github.com/hboutemy/maven-wrapper = the initial wrapper 
donation with 4 commits to switch to Apache, replace provisio to assembly, add 
maven-wrapper-plugin and document
   - site: https://maven.apache.org/wrapper-archives/wrapper-LATEST/
   
   This approach of wrapper does not need any releases when new Maven versions 
are released, and can work with any version from the past and any Maven 
SNAPSHOT (like the original donation)
   
   Getting identical features of installed `mvnw` in a project Git vs 
downloaded Maven distribution `mvn` will be part of MWRAPPER-16 = stop trying 
to re-implement `mvn` logic in `mvnw` to launch a JVM and Maven core, but call 
mvn = the only solution to get consistency
   
   all, please review: in the end, I expect to create a maven-wrapper.git 
repository containing my initial work (that contains initial donation), and 
we'll track future features an release normally in MWRAPPER Jira


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-21 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732






-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-20 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732


   wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) 
does not help on evolving with MWRAPPER-16
   
   please think again: scripts released as part of Maven core do not help to 
have consistency between wrapper scripts copied to project Git and scripts from 
downloaded Maven distribution = the right objective we share. It just helps on 
their maintenance in ASF Git (between maven.git and maven-wrapper-plugin.git), 
at the cost of a confusing release cycle and limitation on possible target 
Maven version (future Maven 4 only)
   
   but at least, I can create MWRAPPER-16 branch to be merged to MWRAPPER-14: 
it's just sad to not be able to work in a constructive way


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-20 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732


   wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) 
does not help on evolving with MWRAPPER-16
   
   please think again: scripts released as part of Maven core do not help to 
have consistency between wrapper scripts copied to project Git and scripts from 
downloaded maven distribution = the right objective we share. It just helps on 
their maintenance in ASF Git (between maven.git and maven-wrapper-plugin.git), 
at the cost of a confusion release cycle and limitation on possible target 
Maven version (future Maven 4 only)
   
   but at least, I can create MWRAPPER-16 branch to be merged to MWRAPPER-14: 
it's just sad to not be able to work in a constructive way


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-11-20 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-974664732


   wrong logic: not merging MWRAPPER-14 (and not releasing a usable wrapper) 
does not help on evolving with MWRAPPER-16
   
   please think again: scripts released as part of Maven core do not help to 
have consistency between wrapper scripts copied to project Git and scripts from 
downloaded maven distribution = the right objective we share. It just helps on 
their maintenance in ASF Git, at the cost of a confusion release cycle and 
limitation on possible target Maven version (future Maven 4 only)
   
   but at least, I can create MWRAPPER-16 branch to be merged to MWRAPPER-14: 
it's just sad to not be able to work in a constructive way


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-10-25 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-951301704


   I completely value the work done to sync mvn and mvnw: syncing again is just 
about copying the 6 partial scripts to 
`maven-wrapper-distribution/src/assembly/maven/`.
   
   on releasing, there is only 1 simultaneous release for the 3 artifacts: 
wrapper, wrapper distribution and wrapper-plugin = the full wrapper, clearly 
separate from the Maven distribution. It is really simple and logical.
   And there won't be many releases in the future, because everything is 
independant from Maven version.
   
   with the latest commits, the new wrapper is working well with whatever Maven 
version


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] [maven-wrapper-plugin] hboutemy edited a comment on pull request #1: [MWRAPPER-14] put all wrapper pieces in one build

2021-10-25 Thread GitBox


hboutemy edited a comment on pull request #1:
URL: 
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-951301704


   I completely value the work done to sync mvn and mvnw: syncing is just about 
copying the 6 partial scripts.
   
   on releasing, there is only 1 simultaneous release for the 3 artifacts: 
wrapper, wrapper distribution and wrapper-plugin = the full wrapper, clearly 
separate from the Maven distribution. It is really simple and logical.
   And there won't be many releases in the future, because everything is 
independant from Maven version.
   
   with the latest commits, the new wrapper is working well with whatever Maven 
version


-- 
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: dev-unsubscr...@maven.apache.org

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



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org