On 10 Feb 2014, at 2:56 pm, Luke Daley <luke.da...@gradleware.com> wrote:
> http://forums.gradle.org/gradle/topics/java_lang_internalerror_could_not_create_securitymanager_jarjar_org_gradle_process_internal_child_bootstrapsecuritymanager > > Anyone have any ideas? There are possibly several issues here, all with the same symptom. The jvm does a poor job of writing any diagnostics when something goes wrong creating the system SecurityManager, which we use to bootstrap the test process. You might start with getting someone to run with -i, so we can see exactly what jvm args ended up being used to launch the process. It’s not necessarily a problem with the jvm args, though. There might be a problem in our caching so that two processes are stomping over each other when they create the small jar we create to bootstrap, so that the problem happens in one build but then goes away. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
