Fixed
Status Update
No update yet.
Comments
uc...@google.com
rp...@google.com
I don't know avd manager has been updated to support Java 9. As a workaround, I would suggest to use Java 8 in the mean time.
yu...@unity3d.com
I'm working on supporting Java9 in Unity, and I'll have to forward the answer "use java8 in the meanwhile" to millions of our users, which is not really the kind of acceptable solution.
So far, there seems to be a workaround - pass "--add-modules java.xml.bind" to the Java params. I can't modify avdmanager script for all the users, but thinking of passing it in JAVA_OPTS or CMD_LINE_ARGS.
So far, there seems to be a workaround - pass "--add-modules java.xml.bind" to the Java params. I can't modify avdmanager script for all the users, but thinking of passing it in JAVA_OPTS or CMD_LINE_ARGS.
yu...@unity3d.com
I was able to workaround the issue by setting AVDMANAGER_OPTS=--add-modules java.xml.bind - maybe it helps someone.
However we still need the fix please.
However we still need the fix please.
ga...@google.com
At the moment, workaround is to pass --add-modules command to java invocation. E.g.
JAVA_OPTS='--add-modules ALL-SYSTEM' $ANDROID_HOME/tools/bin/avdmanager
Once we start shipping JDK9 with the IDE, we can also compile the SDK tools with -target 9.
JAVA_OPTS='--add-modules ALL-SYSTEM' $ANDROID_HOME/tools/bin/avdmanager
Once we start shipping JDK9 with the IDE, we can also compile the SDK tools with -target 9.
ga...@google.com
ar...@gmail.com
Can you please suggest a revision with the fix? Using the SDK revision 3859397 running sdkmanager shows me the same error message. sdklib says it is at 26.0.0 though (./tools/lib/sdklib-26.0.0-dev.jar). Is it possible to update it somehow?
jb...@google.com
It looks like the fix Ivan mentioned does resolve the issue, but we haven't released it yet. We should, though, so I'll look into that.
ar...@gmail.com
It would be great since macOS Homebrew Cask uses the JDK 9 at this point (maybe even 10) and I guess most Linux distributions provide it as well.
BTW, what package should be updated to take advantage of the fix in the future?
BTW, what package should be updated to take advantage of the fix in the future?
ar...@gmail.com
Sorry, but it is getting frustrating. It is the end of 2018, we have JDK 11 right now and the SDK tools were released over a year ago (https://developer.android.com/studio/releases/sdk-tools ). Please, pretty please with a cherry on top — release the update so we can remove nasty hacks locally.
ja...@google.com
jo...@omnidapps.com
Are there any plans to remove the need to use this library? It seems that the use of this library has been deprecated as of Java 9 and removed entirely as of Java 11
https://openjdk.java.net/jeps/320#Java-EE-modules
https://stackoverflow.com/questions/52502189/java-11-package-javax-xml-bind-does-not-exist
se...@gmail.com
sdkmanager has the same problem:
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 5 more
The workaround from #5 doesn't work on OpenJDK 11 because java.xml.bind has been removed.
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 5 more
The workaround from #5 doesn't work on OpenJDK 11 because java.xml.bind has been removed.
jb...@google.com
As mentioned in #8, the fix is checked in but (still) not released.
(For internal people, go/commandlinesdk is the proposal, but I'm not sure what its status is at this point).
(For internal people, go/commandlinesdk is the proposal, but I'm not sure what its status is at this point).
ra...@google.com
I think we should revert that hack, because as mentioned above, it won't work on JDK11. We should simply add the jaxb dependency and adjust classpaths (like upstream IntelliJ).
ar...@gmail.com
"go/commandlinesdk" sounds like a Go-based implementation and I like it.
jb...@google.com
This is released in the new cmdline-tools component, currently in canary. Install via:
sdkmanager --channel=3 'cmdline-tools;1.0-alpha01'
or
sdkmanager --channel=3 'cmdline-tools;latest'
sdkmanager --channel=3 'cmdline-tools;1.0-alpha01'
or
sdkmanager --channel=3 'cmdline-tools;latest'
ha...@google.com
This is not fixed.
The most recent version onhttps://developer.android.com/studio/#command-tools (https://developer.android.com/studio/releases/sdk-tools ) is still from September 2017. `sdkmanager` fails to run on my new Macbook. I am not even sure where to find Java 8.
The most recent version on
ar...@gmail.com
AdoptOpenJDK has a variety of versions available: https://github.com/AdoptOpenJDK/homebrew-openjdk
I hope you’ll have a better luck with pushing right buttons than all of us. Being inside Google should help, right. Right?
I hope you’ll have a better luck with pushing right buttons than all of us. Being inside Google should help, right. Right?
[Deleted User] <[Deleted User]>
It's available in canary (--channel=3) but still hasn't been released to stable. Unfortunately this issue complicates our CI environments because they need avdmanager patches for JAXB support before builds can proceed. We're hoping this can get released soon so we can begin using Robolectric 4.3 which dropped support for JDK 8 and requires JDK 9+.
jb...@google.com
The current plan is for this to be pushed to stable along with studio 3.6.
as...@gmail.com
Just ran into this bug. Tried to install canary to run the new tool but didn't work - guess I'll be downgrading Java tomorrow.
jb...@google.com
What was the issue with the new tool?
pa...@gmail.com
Regarding #20, Now that AS 3.6 is stable, are there plans for updates for sdkmanager and avdmanager?
jb...@google.com
cmdline-tools;1.0 is available in stable now. It contains an updated sdkmanager and avdmanager.
[Deleted User] <[Deleted User]>
jb...@google.com
no problem... sorry it took 2.5 years :-/
sa...@peilicke.de
The new tools can be fetched via AS' SDK Manager directly. You'd have to adjust your PATH as well, for example https://github.com/saschpe/dotfiles/blob/master/.zshrc#L62
jb...@google.com
It's also available in the "Command Line Tools Only" section on https://developer.android.com/studio .
ad...@gmail.com
Can anyone confirm this working? I'm using this download:
https://dl.google.com/android/repository/commandlinetools-linux-6200805_latest.zip
However when I run (JDK 11 environment):
wget --quiet --output-document=sdk-tools-linux.ziphttps://dl.google.com/android/repository/commandlinetools-linux-6200805_latest.zip
unzip sdk-tools-linux.zip -d android-sdk-linux
ANDROID_HOME=$PWD/android-sdk-linux
PATH="$PATH:$ANDROID_HOME/tools:$ANDROID_HOME/tools/lib:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools"
android-sdk-linux/tools/bin/sdkmanager --sdk_root=${ANDROID_HOME} "tools"
android-sdk-linux/tools/bin/sdkmanager "platforms;android-29"
I get
"Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 5 more"
However when I run (JDK 11 environment):
wget --quiet --output-document=sdk-tools-linux.zip
unzip sdk-tools-linux.zip -d android-sdk-linux
ANDROID_HOME=$PWD/android-sdk-linux
PATH="$PATH:$ANDROID_HOME/tools:$ANDROID_HOME/tools/lib:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools"
android-sdk-linux/tools/bin/sdkmanager --sdk_root=${ANDROID_HOME} "tools"
android-sdk-linux/tools/bin/sdkmanager "platforms;android-29"
I get
"Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 5 more"
al...@gmail.com
I can confirm that it's working. Had to revert though because of Robolectric bugs. Also Android Studio has a known issue with JDK9+
jb...@google.com
Ok, I see what's happening, this is interesting:
- When you download and unzip the package like that, the directory into which it is put is not the same as what we would get if it were installed via sdkmanager. In this case, it goes into "tools," whereas it's expected to be in cmdline-tools/1.0.
- When sdkmanager runs, it notices that the unzipped stuff looks like a package, and (incorrectly, filed 150943631) thinks that this package is called "tools"
- Then you install "tools", which is the obsolete version of the tools you just downloaded. The obsolete version has a higher version than what's installed, though, since the new version is 1 and the old version was based on the corresponding android platform version (sort of, at some point), so since we think we're upgrading what's there, the new tools is overwritten (this actually happens even if we were to correctly determine the package path in the previous step. Filed 150944411).
- Then you run sdkmanager again, but this time you're running the old sdkmanager, which doesn't work (as reported initially here).
Probably you should just not install "tools". Also it would be helpful if you renamed the "tools" directory that comes from the zip to something else before starting out (filed 150946939).
Also I filed 150942306 which I ran into while testing using an incomplete version of the steps in #30.
- When you download and unzip the package like that, the directory into which it is put is not the same as what we would get if it were installed via sdkmanager. In this case, it goes into "tools," whereas it's expected to be in cmdline-tools/1.0.
- When sdkmanager runs, it notices that the unzipped stuff looks like a package, and (incorrectly, filed 150943631) thinks that this package is called "tools"
- Then you install "tools", which is the obsolete version of the tools you just downloaded. The obsolete version has a higher version than what's installed, though, since the new version is 1 and the old version was based on the corresponding android platform version (sort of, at some point), so since we think we're upgrading what's there, the new tools is overwritten (this actually happens even if we were to correctly determine the package path in the previous step. Filed 150944411).
- Then you run sdkmanager again, but this time you're running the old sdkmanager, which doesn't work (as reported initially here).
Probably you should just not install "tools". Also it would be helpful if you renamed the "tools" directory that comes from the zip to something else before starting out (filed 150946939).
Also I filed 150942306 which I ran into while testing using an incomplete version of the steps in #30.
[Deleted User] <[Deleted User]>
I reported https://issuetracker.google.com/issues/150327399 on Feb 26 for an issue which downgrades SDK dependencies from 1.0.0 (new versioning scheme) to 26.x (old versioning scheme). I'm not sure whether the issue I filed is a dupe of the issues mentioned in #32 but if it is, feel free to close it.
jb...@google.com
If your original version of the new tools was installed by unzipping manually, it's likely that the issue you saw was because of the combination of issues mentioned above. I'm going to assume that and close the bug as a dup--please let me know if that's incorrect.
ja...@googlemail.com
Using a fresh installation of Android SDK this error still occurs. I don't see a reason why adding the required Jaxb-XML libraries takes so much time?
For details see for example herehttps://stackoverflow.com/a/55982976/150978
Just add them and avdmanager will be usable with all Java versions again.
Or is the general plan to wait for 2023 when finally Java 8 reaches it's end-of-life?
For details see for example here
Just add them and avdmanager will be usable with all Java versions again.
Or is the general plan to wait for 2023 when finally Java 8 reaches it's end-of-life?
jb...@google.com
This is already fixed. Are you using "tools" or "cmdline-tools"? "tools" is deprecated and hasn't been updated in a long time, but "cmdline-tools" is getting regular releases now.
ja...@googlemail.com
If the whole "tools" package is deprecated why is it then installed by default when I install Android Studio + Android SDK?
I just test this, download newest Android Studio, install it and start it then Android SDK will be installed and "tools" package is installed.
I just test this, download newest Android Studio, install it and start it then Android SDK will be installed and "tools" package is installed.
sa...@peilicke.de
I couldn't agree more. With tools remaining installed by default, building OCI containers containing Android SDK and cmdline-tools is a PITA:
As you can see, a lot of extra ceremony is necessary. Because the default releases still contain tools, I need a container running Java 8 to execute sdkmanager "cmdline-tools;latest". Then I can actually build a container based on Java 11 (which is necessary due to Robolectric, etc..) that now sports cmdline-tools. Madness...
jb...@google.com
In that dockerfile you're downloading "tools" explicitly and then using it to download cmdline-tools. You could just download cmdline-tools from the get-go. You can find the url for the cmdline-tools package at https://developer.android.com/studio#downloads (you have to click the link, and then the download button in the license agreement is the actual link).
We shouldn't be installing "tools" by default in recent versions of studio. Let me check to see if we still are by accident.
We shouldn't be installing "tools" by default in recent versions of studio. Let me check to see if we still are by accident.
sa...@peilicke.de
When downloading commandlinetools-linux-6609375_latest.zip from
./tools/bin/sdkmanager --list
Warning: Could not create settings
java.lang.IllegalArgumentException
at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.<init>(SdkManagerCliSettings.java:428)
at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.createSettings(SdkManagerCliSettings.java:152)
at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.createSettings(SdkManagerCliSettings.java:134)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:57)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Usage:
...
jb...@google.com
Shoot, this is fixed in the current stable release of cmdline-tools, but it looks the cmdline-tools link on that page wasn't updated when studio 4.1 went stable. I'll look into getting it fixed.
sa...@peilicke.de
Thanks.
jb...@google.com
As to "tools" being installed by default with studio, it looks like it currently still is, because the new version of the first run wizard (that doesn't install "tools") isn't ready yet, and the old version is deprecated and not being updated.
(This is the story of life within google, and apparently it sometimes affects the outside world as well...)
I can ask about when the new version will be ready, and maybe update the old version if it won't be soon.
(This is the story of life within google, and apparently it sometimes affects the outside world as well...)
I can ask about when the new version will be ready, and maybe update the old version if it won't be soon.
jb...@google.com
The download page is updated now.
va...@gmail.com
is it fixed ?
because sdkmanager --list
still result in below error in windows 10 sdk downloaded today (04-02-2021) by newly installed android studio (4.1.2)
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:606)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:168)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
because sdkmanager --list
still result in below error in windows 10 sdk downloaded today (04-02-2021) by newly installed android studio (4.1.2)
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:606)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:168)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
jb...@google.com
Are you using the version from "tools" or from "cmdline-tools"?
As mentioned in
As mentioned in
ja...@gmail.com
What is the best way to fix this?
Going tohttps://developer.android.com/studio/releases/cmdline-tools mentions:
// Beta channel
sdkmanager 'cmdline-tools;latest' --channel=1
// Canary channel
sdkmanager 'cmdline-tools;latest' --channel=3
Bothhttps://issuetracker.google.com/issues/67495440#comment40 and https://issuetracker.google.com/issues/67495440#comment5 do not work with Java 11.
Going to
// Beta channel
sdkmanager 'cmdline-tools;latest' --channel=1
// Canary channel
sdkmanager 'cmdline-tools;latest' --channel=3
Both
jb...@google.com
If you download from https://developer.android.com/studio#downloads or download "Android SDK Command-line Tools" from the Android Studio SDK manager and then run "cmdline-tools/bin/sdkmanager" (not tools/bin/sdkmanager), you shouldn't have a problem.
If you do, please let me know where you downloaded from, what platform you're on, and what exact command you ran and from where.
If you do, please let me know where you downloaded from, what platform you're on, and what exact command you ran and from where.
bo...@gmail.com
sudo snap install android-studio --classic
ran today with fresh install and ran into the same problem with tools being downloaded rather than cmdline-tools.
ran today with fresh install and ran into the same problem with tools being downloaded rather than cmdline-tools.
[Deleted User] <[Deleted User]>
Hey peeps, just saw this. It works after I am using the one in `cmdline-tools`, why is the deprecated one is being installed? It took couple of hours in our team to check why is it not accepting java 11 :(
jb...@google.com
Studio no longer requires or installs "tools" explicitly. However, unfortunately all existing versions of build-tools have a hardcoded dependency on "tools" and so when you install build-tools it will also install tools. This is already fixed in upcoming versions of build-tools.
ma...@gmail.com
Regardless of the historical reasons why tools is still being installed, would you consider:
-
When installing from Android Studio, install "cmdline-tools" by default? I just made a fresh install of BumbleBee and cmdline-tools wasn't there by default. Anyone doing something like
find ~/Library/Android/ |grep sdkmanagerwill end up using a version that's been deprecated for some time. -
When installing from the commandline, provide a curl install script like
curl -s "https://developer.android.com/install.sh" | bash? That would locate the appropriate zip file, setANDROID_HOME, use the same location as what Android Studio, etc...
These 2 things would make sure that consistent locations and environment variables are used as well as simplify the initial setup.
te...@gmail.com
No device definitions are available
Description
C:/android-sdk\ools\\bin\\avdmanager.bat list target -c
Exception in thread \"main\" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.AvdManagerCli.run(AvdManagerCli.java:213)
at com.android.sdklib.tool.AvdManagerCli.main(AvdManagerCli.java:200)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
... 5 more
May also affect other SDK tools we are using, but so far this is the first one.