Default usage somehow ends up using old plugin and wrapper
jnorthrup opened this issue · comments
Somehow you local network configuration does not seem to download the latest wrapper release and hence you are not getting the latest Maven version. I can not reproduce this on my setup and it seems isolated to your setup.
Try to install the wrapper with mvn directly and see if that makes a difference. Beyond that check what you proxy config and such is..
Wow ... just tried again and I do indeed get the problem. Not sure whats going on to be honest. I will update the docs to include the version.. then it should work.
And in parallel I will try to figure out what is going on..
Maven metadata in Central is correct. http://repo.maven.apache.org/maven2/io/takari/maven/maven-metadata.xml
If you wipe the local Maven repo content in io/takari/maven it works correctly and loads the latest even without specifying. This might be a Maven bug..
the updated README is probably perfect.
i did some digging.
something in the old lineage was sticky.
now run from ./mvnw 0.4.2
success?
yes but.... evil lurks...
jim@jim-Lenovo-ideapad-Y900-17ISK:~/kbrprime-pwa$ cat pom.xml
[...]
<repositories>
<repository>
<id>bintray-kotlin-kotlinx</id>
<name>bintray</name>
<url>https://kotlin.bintray.com/kotlinx</url>
</repository>
</repositories>
does the new README solve things for those who like the "in anger" programming books ?
absolutely! a two button maven wrapper fix for maven-3.6, great job!