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

React-Native Maven is no longer actively updated with releases #6459

Closed
lental opened this issue Mar 15, 2016 · 3 comments
Closed

React-Native Maven is no longer actively updated with releases #6459

lental opened this issue Mar 15, 2016 · 3 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@lental
Copy link

lental commented Mar 15, 2016

Hey all,

I understand that 0.21.0 and higher are now being distributed through npm, however I'd like to suggest that react-native continues to distribute the package through maven,

I work on a library that places a complex UI Widget into the developer's application. By using react-native as a maven dependency, I can ask the developer to add the maven dependency, and not have to bother with all of the react-native npm and other configuration process just to use our library.

From all verisons < 21, My company can create a library that is built using the entire react-native framework, and allow for integration with our library with nothing but the maven dependency, and I have had a great time building it to that point.

I'm treating this as a bug because it's a regression from our original usage of the framework. Is there any chance the Maven repository can continue to be updated?

Thanks

@ide
Copy link
Contributor

ide commented Mar 15, 2016

For maintenance reasons it's unlikely that we'll publish to Maven (or CocoaPods on iOS). Maven significantly slows down the release process since we have to wait a few hours for the artifacts to get distributed, poses permissions problems, and increases the surface area of code to test. If you rely on Maven in your workflow, though, my suggestion is to take the JAR/AAR assets distributed via npm and upload them to Maven yourself.

@mkonicek
Copy link
Contributor

@facebook-github-bot answered

@facebook-github-bot
Copy link
Contributor

Closing this issue as @mkonicek says the question asked has been answered. Please help us by asking questions on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants