Displaying #maven-dev/2017-06-24.log:

Sat Jun 24 06:28:00 2017  hboutemy:Joined the channel
Sat Jun 24 06:46:40 2017  hboutemy:Joined the channel
Sat Jun 24 07:35:20 2017  hboutemy:Joined the channel
Sat Jun 24 08:00:37 2017  tibor_:Joined the channel
Sat Jun 24 08:52:20 2017  rfscholte:Joined the channel
Sat Jun 24 10:28:20 2017  rfscholte:Hi, I'd like to activate --strict-checksums by default locally. Is there really no other option than patching the mvn file?
Sat Jun 24 10:44:38 2017  tibor_:Joined the channel
Sat Jun 24 11:29:33 2017  hboutemy:rfscholte: MAVEN_OPTS?
Sat Jun 24 11:33:16 2017  hboutemy:notice that in mvn Unix shell( not .cmd), there is a MAVEN_CONFIG env parameter that is used
Sat Jun 24 11:33:50 2017  hboutemy:but not consistently between MAVEN_CMD_LINE_ARGS and effective command line
Sat Jun 24 11:34:06 2017  hboutemy:looks like a discrepency we should fix...
Sat Jun 24 12:01:07 2017  rfscholte:no, MAVEN_OPTS is for JVM args, this is a Maven arg
Sat Jun 24 12:01:20 2017  rfscholte:Unrecognized option: --strict-checksums
Sat Jun 24 12:01:36 2017  rfscholte:that's the error when using MAVEN_OPTS
Sat Jun 24 12:24:35 2017  hboutemy:true...
Sat Jun 24 12:25:06 2017  hboutemy:looks like the MAVEN_CONFIG env parameter is a half backed feature
Sat Jun 24 12:52:10 2017  rfscholte:I agree
Sat Jun 24 22:56:39 2017  olamy:Joined the channel

Comments