A completely different approach is to create a local maven repository for appengine sdk and a link that directly and leave everything else intact.
repositories { maven { url 'file://path/to/myCustomRepo' } mavenCentral() }
Thus, this method is easiest if you grab appengine sdk directly from maven.org, because it will be correctly named. ( http://search.maven.org/#artifactdetails|com.google.appengine|appengine-java-sdk|1.9.6|zip ), but select the version that you reference in the assembly file.
About maven repo, you need to configure it correctly. If your downloaded zip is located in /path/to/myCustomRepo , you need to put the zip in the right place: /path/to/myCustomRepo/com/google/appengine/appengine-java-sdk/1.9.6 depending on the version number you are using .
If you only have a zip file in the repository directory, you need to change the downloadSdk line to indicate that everything is available, this is a “zip” with @zip .
downloadSdk "com.google.appengine:appengine-java-sdk: 1.9.6@zip "
If you do not want to use @zip , you can add a simple .pom file (next to .zip) so that the system can correctly identify the link
AppEngine-Java-KFOR-1.9.6.pom
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.google.appengine</groupId> <artifactId>appengine-java-sdk</artifactId> <packaging>zip</packaging> <version>1.9.6</version> </project>
source share