Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AndroidX #488

Closed
wants to merge 11 commits into from
Closed

AndroidX #488

wants to merge 11 commits into from

Conversation

forkch
Copy link
Contributor

@forkch forkch commented Jun 19, 2018

migration to AndroidX

right now i cannot build due to some maven publishing taks which are not working on my machine (or due to the new gradle plugin..)

@forkch forkch mentioned this pull request Jun 19, 2018
testCompileAar "com.android.support:support-v4:$SUPPORT_LIBRARY_VERSION"
testCompileAar "com.android.support:support-v13:$SUPPORT_LIBRARY_VERSION"
testCompileAar 'androidx.legacy:legacy-support-v4:1.0.0-alpha3'
testCompileAar 'androidx.legacy:legacy-support-v13:1.0.0-alpha3'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Create a version code at gradle.properties

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TO: @hotchemi @mannodermaus

I was thinking we are still keep android support library's support. Do we want to drop the support of support library?

@@ -26,7 +24,7 @@ import permissions.dispatcher.samplekotlin.R
* Implementation is based directly on the documentation at
* http://developer.android.com/guide/topics/media/camera.html
*/
class CameraPreviewFragment : Fragment() {
class CameraPreviewFragment : androidx.fragment.app.Fragment() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do not import?

@forkch
Copy link
Contributor Author

forkch commented Jun 20, 2018

I've fixed the mentioned issues (imports and versioning) and fixed the travis build by copying the licences to $ANDROID_HOME/licences

It is failing now due to the publishing plugin. I don't know how you usually deal with this.

@hotchemi
Copy link
Member

hotchemi commented Jun 21, 2018

Might be related to https://github.com/novoda/bintray-release could you try to update the ver?

@forkch
Copy link
Contributor Author

forkch commented Jun 21, 2018

no luck...bintray-release does not seem to support gradle-4.6 but the android-gradle plugin for AndroidX should be the 3.2.0-alpha*

novoda/bintray-release#177

@hotchemi
Copy link
Member

Umm.. 🤔
I found kind of official plugin and seems there is a PR for that but haven't merged yet.
bintray/gradle-bintray-plugin#230

@forkch
Copy link
Contributor Author

forkch commented Jun 21, 2018

Unfortunately I have no resources at the moment to look into bintray (have not yet deployed any artifacts to any kind of artifactory :-)).

@forkch
Copy link
Contributor Author

forkch commented Jun 21, 2018

Sorry my Android Studio Canary was terribly broken and did show me successful tests and launched the sample app fine. There were a lot of compile issues in the code which Android Studio did not show me :-(

Now the project should compile fine but I could not figure out how to make the test-v13 run so I ignored them for now.

I would actually suggest to maybe release the AndroidX support as a new library version 4.x.y and completely drop the support for the old support-lib.

@hotchemi
Copy link
Member

Umm ok, it would be actually a huge change so it might be better to be addressed by @permissions-dispatcher/maintainers 🤔Really sorry to say that but this is actually a great work!

@shiraji
Copy link
Member

shiraji commented Jun 26, 2018

Let me take over this work.

@shiraji shiraji mentioned this pull request Jun 26, 2018
3 tasks
@shiraji
Copy link
Member

shiraji commented Jun 26, 2018

@forkch if you don't mind, could I change your commit author mail address to your GitHub email address? This change leads to associate your commit with your GitHub account. See #494

@forkch
Copy link
Contributor Author

forkch commented Jun 26, 2018

Sure no problem!

@shiraji
Copy link
Member

shiraji commented Jun 26, 2018

Done. See #494

I will close this PR since all @forkch works are there. Thank you for your contribution!

@shiraji shiraji closed this Jun 26, 2018
@hotchemi
Copy link
Member

Thank you @forkch !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants