A few days ago I picked up the latest milestone-7 nightly release to see if it resolved a bug I ran into (it did), but ended up regressing another part of my build which is working in milestone-6.
Just want to understand the protocol here – Should we be reporting to the forum regressions we run into with these nightly releases, or wait till there is a call for users to officially give their builds a try?
Also – Is there a particular recommended way perhaps using the gradle wrapper to automatically get the lastest available nightly release of Gradle? I’d like to throw that into a CI build to run nightly so that we can can proactively monitor our builds against the upcoming next milestone release?
PS – The regression I ran into occurs when running the compileTestJava task in my project where I use testng.
I get the following error:
FAILURE: Build failed with an exception. * What went wrong: Could not resolve all dependencies for configuration ':GoPaymentServer:testCompile'. Cause: Artifact 'org.testng:testng:6.1.1:jdk15@jar' not found * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED
No where in my dependency section do I have this particular dependency spec. Instead, I have:
I’m not sure where the jdk15 classifier is coming from? Perhaps there are some changes going on in milestone-7 for testng? Near as I can tell, testng 5.11 was the last version to use jdkXX classifiers.