Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- <?xml version="1.0" encoding="UTF-8"?>
- <issues format="4" by="lint 3.1.0">
- <issue
- id="InvalidPackage"
- severity="Error"
- message="Invalid package reference in library; not included in Android: `java.awt.datatransfer`. Referenced from `jline.console.ConsoleReader`."
- category="Correctness"
- priority="6"
- summary="Package not included in Android"
- explanation="This check scans through libraries looking for calls to APIs that are not included in Android.

When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.

This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.">
- <location
- file="/builds/MYPROJECT//.gradle/caches/modules-2/files-2.1/my.company/submodule/2.3.0/fb1c122217dea84955b270e1d0d95e3cb59a64d2/submodule-2.3.0.jar"/>
- </issue>
- <issue
- id="InvalidPackage"
- severity="Error"
- message="Invalid package reference in library; not included in Android: `java.awt.event`. Referenced from `jline.console.ConsoleReader`."
- category="Correctness"
- priority="6"
- summary="Package not included in Android"
- explanation="This check scans through libraries looking for calls to APIs that are not included in Android.

When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.

This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.">
- <location
- file="/builds/MYPROJECT//.gradle/caches/modules-2/files-2.1/my.company/submodule/2.3.0/fb1c122217dea84955b270e1d0d95e3cb59a64d2/submodule-2.3.0.jar"/>
- </issue>
- <issue
- id="InvalidPackage"
- severity="Error"
- message="Invalid package reference in library; not included in Android: `java.awt`. Referenced from `jline.console.ConsoleReader`."
- category="Correctness"
- priority="6"
- summary="Package not included in Android"
- explanation="This check scans through libraries looking for calls to APIs that are not included in Android.

When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.

This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.">
- <location
- file="/builds/MYPROJECT//.gradle/caches/modules-2/files-2.1/my.company/submodule/2.3.0/fb1c122217dea84955b270e1d0d95e3cb59a64d2/submodule-2.3.0.jar"/>
- </issue>
- <issue
- id="InvalidPackage"
- severity="Error"
- message="Invalid package reference in library; not included in Android: `javax.script`. Referenced from `potx.shell.js.JsCreator`."
- category="Correctness"
- priority="6"
- summary="Package not included in Android"
- explanation="This check scans through libraries looking for calls to APIs that are not included in Android.

When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.

This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.">
- <location
- file="/builds/MYPROJECT//.gradle/caches/modules-2/files-2.1/my.company/submodule/2.3.0/fb1c122217dea84955b270e1d0d95e3cb59a64d2/submodule-2.3.0.jar"/>
- </issue>
- <issue
- id="InvalidPackage"
- severity="Error"
- message="Invalid package reference in library; not included in Android: `javax.xml.stream`. Referenced from `potx.shell.HtmlCreator`."
- category="Correctness"
- priority="6"
- summary="Package not included in Android"
- explanation="This check scans through libraries looking for calls to APIs that are not included in Android.

When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.

This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.">
- <location
- file="/builds/MYPROJECT//.gradle/caches/modules-2/files-2.1/my.company/submodule/2.3.0/fb1c122217dea84955b270e1d0d95e3cb59a64d2/submodule-2.3.0.jar"/>
- </issue>
- <issue
- id="TrustAllX509TrustManager"
- severity="Warning"
- message="`checkClientTrusted` is empty, which could cause insecure network traffic due to trusting arbitrary TLS/SSL certificates presented by peers"
- category="Security"
- priority="6"
- summary="Insecure TLS/SSL trust manager"
- explanation="This check looks for X509TrustManager implementations whose `checkServerTrusted` or `checkClientTrusted` methods do nothing (thus trusting any certificate chain) which could result in insecure network traffic caused by trusting arbitrary TLS/SSL certificates presented by peers.">
- <location
- file="/builds/MYPROJECT/securitymodule/dev/tls/Tls$2.class"/>
- </issue>
- <issue
- id="TrustAllX509TrustManager"
- severity="Warning"
- message="`checkServerTrusted` is empty, which could cause insecure network traffic due to trusting arbitrary TLS/SSL certificates presented by peers"
- category="Security"
- priority="6"
- summary="Insecure TLS/SSL trust manager"
- explanation="This check looks for X509TrustManager implementations whose `checkServerTrusted` or `checkClientTrusted` methods do nothing (thus trusting any certificate chain) which could result in insecure network traffic caused by trusting arbitrary TLS/SSL certificates presented by peers.">
- <location
- file="/builds/MYPROJECT/securitymodule/dev/tls/Tls$2.class"/>
- </issue>
- </issues>
Advertisement
Add Comment
Please, Sign In to add comment