@olleolleolle sure let's try it.

Are the m2 caches really working? Seems like a lot of downloading. (I'm not used to Maven work, so I may be way off.)

Seen a few other Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=2G; support was removed in 8.0 but they're perhaps connected to the JAVA_OPTS?

@olleolleolle our build does download lots of crap once a day so it might be that build firing on appveyor...or not?

Are the m2 caches really working? Seems like a lot of downloading. (I'm not used to Maven work, so I may be way off.)

the maven cache is emptied on AppVeyor when the pom file is updated:

cache:
  - C:\Users\appveyor\.m2\repository -> pom.xml

Note; AppVeyor lacks a way to purges the cache manually unlike Travis-CI

@mprins would it be possible to associate the cache with pom.rb - as the current pom.xml is obsolete and there were already question whether or not to get rid of it.

Just change that line in the appveyor.yml to point to pom.rb instead

What is the needed amount of RAM to run the test suite in AppVeyor?

yaaay - finally a 💚 ci :) ... @olleolleolle maybe do the OPTS similar to how its done on travis-ci
there's JAVA_OPTS (for the suite - starts low due spawn-ed sub rubies) https://github.com/jruby/jruby/blob/master/.travis.yml#L31 (and MAVEN_OPTS for mvn) - hopefully similar values will do on Windows.

(... but if its green already than this is better than the current setting -> can be tuned later)

@kares An issue that I suspect is: AppVeyor is not run on all pushes? I can only see it run on my first commit to this PR.

And, thank you for the values tips - I changed the YAML config for AppVeyor to that.

Ugh: https://github.com/jruby/jruby/blob/master/.travis.yml#L12-L13 Should I recreate that logic?

aaah, bumper - do not know much about AppVeyor setup ... guess @enebo will have to approve the merge.
wouldn't worry about the MAVEN_OPTS mangling much -> unless the Windows CI runs into some trouble ...

@olleolleolle that referenced logic in the travis.yml does some java 7 specific setup; but on Appveyor you're just testing with java 8, so no point in trying to emulate that.

@mprins For Java8 on AppVeyor, should I add -XX:MaxMetaspaceSize=200M -XX:CompressedClassSpaceSize=200M to the MAVEN_OPTS?

Also: Do I need to have the data from JAVA_OPTS also in the MAVEN_OPTS?