Remove react-native package from maven central and jcenter

[carlospaulino]

Description

A really old version of react-native is being hosted on maven central and jcenter.

Please remove it to avoid confusions.

http://search.maven.org/#artifactdetails%7Ccom.facebook.react%7Creact-native%7C0.20.1%7Caar
https://bintray.com/bintray/jcenter/com.facebook.react%3Areact-native

Additional Information

• React Native version: 0.20.1
• Platform: Android

[ide]

@mkonicek What do you think about removing this? I believe it's been over a year since the last publish.

[clarle]

Just curious, what's the reasoning behind not publishing it to Maven Central / JCenter regularly?

[ide]

Unlike most other libraries, RN has inherently coupled JS+Java and JS+Obj-C so we want to distribute related code together in the interest of high cohesion. Additionally the build system is JS-centric and works out of node_modules, so we want to distribute the JS using npm more than we want to distribute the Java using Maven or ObjC using CocoaPods.

We also want to keep the deployment process simple hence publishing to just one package repository, so the pragmatic place we've landed is to distribute all the code through npm and let people use Gradle or CocoaPods locally for linking, just not distribution. There are some downsides to this but it's the tradeoff we've made and are willing to commit to.

[pyankoff]

I strongly support the idea of removing react-native@0.20 from maven. It masks gradle linking problems and creates errors like these which are harder to debug:

https://github.com/idehub/react-native-billing/issues/42
evollu/react-native-fcm#235

[petterh]

An argument for publishing versions of React Native through Maven

We have a scenario where several existing Android app will consume a reusable React Native component. However, none of owners of the existing apps want to add yet another tech (npm) to their build system, yet they have a dependency on the React Native native components (basically what's in node_modules/react-native/android).

If React Native is not publicly available through Maven, we need to distribute this ourselves. Which isn't too hard, but getting it through Maven would be nicer, IMO.

Though obviously it needs to be up-to-date. Having ancient versions hanging about is, as @pyankoff mentioned above, troublesome.

[urjitbhatia]

We have a similar setup as @petterh - a common RN component library that we want to reuse without having to install node_modules and the rest of the react setup in all the apps. We are generating an aar artifact but there are still some places in the main app we need to refer to com.facebook.react stuff.
Not sure what a good way out of that is right now.

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

[gengjiawen]

This is need to be done, because it bring to much surprise, even for android developer.

[gengjiawen]

You doesn't update your dependency, but for one day, you code won't build simply because react native push one version to jcenter.

@grabbou @hramos Can you do something about this ?

[gengjiawen]

For anyone want to hack this, you need to config your root build.gradle like this. 0.51.1 is the version you want (the one you use in package.json).

configurations.all {
        resolutionStrategy.eachDependency { details ->
            if (details.requested.group == 'com.facebook.react') {
                details.useVersion "0.51.0"
            }
        }
 }

[gengjiawen]

And for the argument bringed by @petterh , you need not distribute. Just use npm, it's quite easy (a few lines of gradle config) , just as the react native template show.

[hramos]

Related to #19259.