Firebase SDK 9.0.0 is exciting but I cannot find the plain java version of its library. The older 2.5.2 doc used to have separate SDK for Android and plain JVM, I cannot find this information in the new doc.
Is there a way to use this SDK for non-Android project, like say, JavaFX? If not, will I run into a problem for still using the older 2.5.2 SDK on my JavaFX project?
Yes you can. Look under Server in the docs instead of the Android section.
We publish the Firebase Java SDK to the Maven central repository. To
install the library, you can simply declare it as a dependency in your
build.gradle file:
dependencies {
compile 'com.google.firebase:firebase-server-sdk:[3.0.0,)'
}
If you use Maven
to build your application, you can add the following dependency to
your pom.xml:
<dependency>
<groupId>com.google.firebase</groupId>
<artifactId>firebase-server-sdk</artifactId>
<version>[3.0.0,)</version>
</dependency>
Related
I am very new at Java for Android and I am using Electric Eel version of Android Studio. Course when I use learn android says that ı have to dwnload Android Support Repository. It says that I can download from SDK Manager but I couldn't find it there. Would you help me to find?
enter image description here
I want to download Android Support Repository. I found something different about The support repository is long gone and no longer needed. Is that true?
android support libraries are now available through Google's Maven repository
To add a Support Library to your application project:
Include Google's Maven repository in your project's settings.gradle file
check this link for more information
I'm trying to find out how to add eBay Java SDK for eBay REST API to the SCALA 2.13.8 SBT project. How to add eBay JAVA SDK to the SBT or Maven project?
eBay JAVA SDK page: https://developer.ebay.com/develop/ebay-sdks/java-sdk
Available versions for download are 1131 and 1113. According to Trading API Release Notes, they are outdated, the up-to-date version is 1257.
Trading API Release Notes: https://developer.ebay.com/DevZone/XML/docs/ReleaseNotes.html
I've looked on the mvnrepository.com, but this SDK is not represented there: https://mvnrepository.com/artifact/com.ebay?p=1
Furthermore, I can't find a source code on eBay GitHub: https://github.com/orgs/eBay/repositories?q=sdk&type=all&language=java&sort=
The download for that Java SDK includes the source and a pom.xml in the maven_build directory. You can use that to build the dependency and have it in your local maven repo.
From there, you can either set that build up as a maven module to get built before your code, or you can take the jar and commit it with your code and use maven to install it at build time.
Here is how you can use maven to install it from an in-project repo
Maven: best way of linking custom external JAR to my project?
I am really confused about how gradle works with android subproject and simple server-java subproject tied to Project.
Android is using not the latest version of gradle, but my server app can use it.
Should I use the minimum version that supports all modules, or can I somehow edit the build file for each module?
I am trying to learn more about DWOLLA, using their sandbox. I am mainly interested in using their access API with an android APPLICATION. The Dwolla API Docs says, "Download and build the JARs to use this library. Maven is required to manage this project's dependencies." The following are the links:
git clone https://github.com/Dwolla/dwolla-swagger-java
cd dwolla-swagger-java
mvn install package
How do I integrate the above in an android application/project. My assumption is that I would have to do it in gradle but I am not certain.
Android apps' dependencies are managed with Gradle.
The default repository is JCenter.
The Dwolla SDK is found here.
All you have to do is, on that page, click on 'gradle' and you get the line that you have to your app's build.gradle file.
Here it is compile 'com.dwolla:dwolla-java-sdk:2.0.9'.
Add that to your app module's build.gradle under dependencies, refresh the project and you should be fine.
I'm using grails 2.5 and was using grails spring websockets in my project and everything was ok. Now, as I want to implement login with Google added the maven dependency to BuildConfig for google api client:
compile 'com.google.api-client:google-api-client:1.20.0'
And now, when I run the app I get this error
java.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()
This is because there's a conflict between the Jackson libraries that spring websocket plugin and google api client are using.
As I could see, it looks like google api is using an outdated version of jackson.
Is it possible to exlude jackson to be imported from a maven dependency? I know that from a grails plugin is possible adding 'exclude'. But it doesn't seem to work for a maven dependency, I've added this but with no luck:
compile 'com.google.api-client:google-api-client:1.20.0', { excludes "com.google.api-client:google-api-client-jackson2:1.20.0" }
Just to remind, the google api client dependency is under 'dependencies' group in BuildConfig, which is using mavenCentral() to get the dependencies, not under 'plugins'.
Does anybody know how could I fix this?
thanks
EDIT: Probably not ideal, but I could solve this problem just adding the latest jackson dependency
compile 'com.google.api-client:google-api-client:1.20.0', {
excludes "com.google.api-client:google-api-client-jackson2:1.20.0"
}
compile 'com.fasterxml.jackson.core:jackson-core:2.7.2'
I don't think what you are trying to do is possible. Exclusions can work for plugins because the source is downloaded and compiled locally. For dependencies, you are using maven, which is downloading jars. You can't tell maven to exclude part of the jar.
The Google code you want to use may depend on other methods of the Jackson version it depends on that are not present in the version you want to use. In that case, if Maven allowed excluding Google's declared version of Jackson, the Google library would not even work. (The same problem would occur for plug-ins if they needed a different version of some library at compile time.)
You could try making your own version of the Google jar that uses your preferred version of Jackson. If it doesn't depend on methods from the older version of Jackson, that could work.