https://kotlinlang.org
Join Slack
Hum :disappointed: Seems there's some packaging issue :disappointed: IDE expect androidx.compose.ui....
# compose
t
Hum 😞 Seems there's some packaging issue 😞 IDE expect androidx.compose.ui.tooling.preview.ComposeViewAdapter for the previews but from RC01-sources.jar the ComposeViewAdapter is still in the normal ui.tooling package 😞
e
There is now ui-tooling and ui-tooling-preview
t
Yes but that one was not migrated to the new package but the IDE expect it in the new one.
Ok so no it's the opposite that one was migrated to a new package but something is still referencing the old one 😞 No idea where it's from
j
IIRC, we moved the maven artifact coordinates of the class, but didn't change the package name. You just need to add the new maven artifact to your maven dependencies as @Eric Ampire [MOD] was alluding to.
t
The package did change from the sources.jar of ui-tooling
And from the doc of the commit https://github.com/androidx/androidx/commit/93d7c4618449a29e5baf5b5e02ceffec9cffc766 there should be no need to add the new artifact (that does not contain that class either BTW)
f
What maven dependency do you need to add? I can't get it to work.
t
There's nothing you can do to fix with maven deps. Seems there was a mistake and the package directive of that class was changed when it should not have been. They either need RC02 with proper packagename or change on the other side.
According to
Copy code
In order to comply with module+packagename guidelines, we moved some classes
from androidx.compose.ui.tooling.preview to androidx.compose.ui.tooling,
since they're supposed to stay in the ui-tooling module.
It's most likely that they should fix the other side that still reference the old package.
t
It's still in 
androidx.compose.ui.tooling.preview
though
oh, not ComposeViewAdapter, yeah
c
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by