Hi, why does artifactory 2.6 generates a build.gradle but not an init.gradle file?
With the generation of a build.gradle artifactory suggests to place infrastructural information into the build-script. The possibility to not provide infrastructural information into the build-script was one of the main-reasons switching from maven to gradle. If I look into the artifactory-wiki there is described to generate the init.gradle-script but in artifactory 2.6 this option is replaced by the build.gradle-script generation option. What was the motivation to change this behaviour? The generated build.gradle-script does not work if I put it into ~/.gradle/init.d and place the generated properties-file in ~/.gradle. I use gradle 1.0-rc-3 on a 64Bit-JVM on Windows 7 if it is relevant. My Artifactory runs on a Ubuntu VM with OpenJDK 1.6 32Bit Is there a trick? Or do I miss something? -- Kind regards Thorsten -- View this message in context: http://forums.jfrog.org/No-more-init-gradle-tp7538445.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
