git clone https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven#change the version in the POM to 1.9.37mvn appengine:devserver
[ERROR] Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc (default) on project helloworld: Execution default of goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc failed: A required class was missing while executing com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc: com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils
package com.google.appengine.repackaged.com.google.api.client.util;
public class StringUtils {
public static final String LINE_SEPARATOR = System.getProperty("line.separator");
public static byte[] getBytesUtf8(String string) {
return com.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string);
}
public static String newStringUtf8(byte[] bytes) {
return com.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes);
}
private StringUtils() {
}
}
package com.google.appengine.repackaged.com.google.api.client.util;
public class StringUtils {
public static final String LINE_SEPARATOR = System.getProperty("line.separator");
public static byte[] getBytesUtf8(String string) {
return com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string);
}
public static String newStringUtf8(byte[] bytes) {
return com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes);
}
private StringUtils() {
}
}
I think this is a bug in GAE. I also think that it can affect deployed instances since GAE uses the latest version in production. I would be interested in knowing if there is a workaround or if we have to wait for the next version?
On Tuesday, May 10, 2016 at 9:24:50 PM UTC-7, Shian Wu wrote:
I got same problem when using GAE java 1.9.37.
It is work with GAE java 1.9.34 before.
After compare source of com.google.appengine.repackaged.com.google.api.client.util.StringUtils , I found it is a little different.
In 1.9.34
package com.google.appengine.repackaged.com.google.api.client.util; public class StringUtils { public static final String LINE_SEPARATOR = System.getProperty("line.separator"); public static byte[] getBytesUtf8(String string) { return com.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string
);< /span>
} public static String newStringUtf8(byte[] bytes) { return com.google.appengine.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes
In 1.9.37);< /span> } private StringUtils() { } }
And I can not find com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils in GAE java 1.9.37package com.google.appengine.repackaged.com.google.api.client.util; public class StringUtils { public static final String LINE_SEPARATOR = System.getProperty("line.separator"); public static byte[] getBytesUtf8(String string) { return com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.getBytesUtf8(string); } public static String newStringUtf8(byte[] bytes) { return com.google.appengine.repackaged.com.google.api.client.repackaged.org.apache.commons.codec.binary.StringUtils.newStringUtf8(bytes); } private StringUtils() { } }I think this is why it can't work.Is this a bug or something I miss when upgrade to GAE java 1.9.37 ? On Wednesday, May 11, 2016 at 12:53:09 AM UTC+8, Paul Mazzuca wrote:When running the following EndPoints example with GAE 1.9.37 as so,I receive the following error:git clone https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven#change the version in the POM to 1.9.37mvn appengine:devserver[ERROR] Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc (default) on project helloworld: Execution default of goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc failed: A required class was missing while executing com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc: com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils
Could an essential EndPoints class have been removed in the latest GAE release, or am I missing something?
Also facing this issue. Any update? It doesn't help that we're running into this while evaluating adoption of AppEngine :(
On Tuesday, 10 May 2016 17:53:09 UTC+1, Paul Mazzuca wrote:
When running the following EndPoints example with GAE 1.9.37 as so,
git clone https://github.com/GoogleCloudPlatform/appengine-endpoints-helloworld-java-maven#change the version in the POM to 1.9.37
< code>mvn appengine:devserver
I receive the following error:[ERROR] Failed to execute goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc (default) on project helloworld: Execution default of goal com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc failed: A required class was missing while executing com.google.appengine:appengine-maven-plugin:1.9.37:endpoints_get_discovery_doc: com/google/appengine/repackaged/com/google/api/client/repackaged/org/apache/commons/codec/binary/StringUtils
Could an essential EndPoints class have been removed in the latest GAE release, or am I missing something?
Fixed in 1.9.38.
Ludo
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/aaaf2d78-4a8a-482d-98cf-58f5ab5c6f45%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.