-
Notifications
You must be signed in to change notification settings - Fork 67
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
Build Failing #3
Comments
Is it okay to build the artifacts with Java 8? That is how Travis is working. If I use Java 6/7 it fails:
|
cc @cbeams for guidance on this so I can release |
Right. JavaFX was first included as part of Java SE beginning with JDK 8. So while it would technically be possible to support most or perhaps all of what's in RxJavaFX on earlier JDKs by including standalone JavaFX distributions on the classpath, I don't see a compelling reason to do so. JDK 8 has been out for a while now, and RxJavaFX is essentially brand new. I don't see any reason not to go forward assuming JDK 8 as a baseline. In short, I'd say ship RxJavaFX 0.1.0 as-is, and with the assumption of JDK 8 or better. That at least creates the opportunity for folks to consume the project easily, and provide feedback if they really need support for earlier JDKs. |
Cool, that simplifies. So I changed to Java 8 and am now getting this:
Need to figure out how to configure it to be headless.
... but due to how Gradle works I need that somehow configured via Gradle I believe. |
I'm not sure why you're still seeing this error—#4 should have fixed it. We had the same |
I copied the source files to a new project and did a simple Gradle build just fine (with RxJava as a dependency). I am not sure what trails you guys are chasing but maybe the Gradle build just needs to be simplified??? |
Hey guys, if you want I can submit a pull request to simplify the Gradle build and let this be buildable again. It may not be what you were trying to accomplish initially, but just hitting Maven Central for the dependencies will at least get this working. Unless... are you trying to target anything other than JavaFX 8? |
It would be nice to make the project build so a 1st version can be deployed to Maven centrale... |
Okay I submitted a pull request. I was not quite sure what @benjchristensen and @cbeams were trying to accomplish and if I omitted anything of importance, but I made a simpler dependency setup and it built for me no problem. |
Is this project going to see some light on maven central some day? @benjchristensen |
Hey guys, until folks get a moment to review the pull request, you are more than welcome to use my fork here. https://github.com/thomasnield/RxJavaFX |
This project needs an owner. No one from Netflix uses or has experience with JavaFX. If someone wants to take over ownership, let me know and I can grant privileges to commit and release. For builds, I recommend getting it working with the Nebula build plugin all other RxJava projects use, otherwise you will be on your own for getting the binary release process working which we have got working very smoothly via Travis -> Bintray -> Maven Central. |
I am somewhat proficient with JavaFX. I'm still learning a lot about RxJava and JavaFX though, so I don't know if I would qualify as someone to administrate over this. I'd recommend getting this on Maven Central though at least, with or without Nebula so the project can start getting interest and support. But let me know if I can do anything to help. |
Actually, if there is nobody else I can at least take stewardship of the project and keep it up to date with RxJava binary releases. I have a huge need for this library and don't mind maintaining it until someone else comes along. |
@thomasnield I have invited you to be a committer so you can take on stewardship of this project. |
Thanks @benjchristensen, I'll help the best I can. If anybody else is following this thread, I propose getting this on Maven Central ASAP to attract interest to the project, even if it means simplifying Gradle dependencies to binaries (which is in my PR). Please let me know if there are any objections by Sunday, and if there are none I'll start getting a release ready. |
I think for you to get to Maven Central I need to update your .travis.yml file so that all the credentials are there for publishing. It needs the setup that RxJava and other projects have for BinTray and Sonatype. |
Okay. Let me know if there are any actions I need to take... |
I've got the pieces in place, but there is some odd build issue that I don't understand. It has nothing to do with releasing. I don't have time right now to figure it out, but it's on my list, unless you can beat me to it. Here's what needs to happen though:
It needs to use the RxJava Nebula plugin, as used by RxJava, RxAndroid and other projects.
This encapsulates all the build and release behavior used by RxJava.
The Travis builds are setup so they should start working as soon as the build is working.
As soon as the project is building via Travis, it will start publishing snapshots to JFrog, This happens via the Travis build via this command: https://github.com/ReactiveX/RxJavaFX/blob/0.x/gradle/buildViaTravis.sh#L9 It will look like this when it works: https://travis-ci.org/ReactiveX/RxJava/builds/74370551#L3692
Releases are done by tagging the repo. This is most easily done by creating a new release via Github: https://github.com/ReactiveX/RxJavaFX/releases When the repo is tagged, it triggers a build in Github and releases via Bintray to Maven Central. This is done via this command: https://github.com/ReactiveX/RxJavaFX/blob/0.x/gradle/buildViaTravis.sh#L11 The first time this is done let me know (or have me do it once things are building), as there is something I need to do on Bintray for the first release to start the process of syncing to Maven Central. After the first one it will be automatic and fully controllable by you. The Git tag represents the version. So, tag it as "0.0.1" of "v0.0.1" to release to maven central as version "0.0.1". |
Okay I'll see if I can make time. I got about 12 things to learn so I'll add this to my agenda. |
I'm working on this right now. I considered some observations by @jpenglert and also found the gradle-rxjava-project-plugin was being called in a deprecated manner. https://github.com/nebula-plugins/gradle-rxjava-project-plugin Still investigating a build failure though. |
Well good news ya'll. I got this to build finally and repaired the Nebula dependencies. I had to do a lot of Googling and found the right setup. One of the unit tests |
Does anybody know why the unit test would fail on Travis but work fine with a local Gradle build? Slightly puzzled over this. The build is working fine now and if this unit test gets resolved I see no reason why we can't deploy to Maven Central. @benjchristensen |
I resolved the unit test, and we officially have a successful travis build. I constructed a |
Okay i tagged the release. This should trigger a Maven Central deployment as @benjchristensen said... |
For some odd reason, it is listing as 0.0.0 instead of 0.0.1 on Maven Central... https://repo1.maven.org/maven2/io/reactivex/rxjavafx/ |
Alright the RxJavaFX library is officially on Maven Central as 0.0.2. |
This is not yet building ... someone who works with JavaFX needs to figure this out.
I can make it build with Java 8, but there must be a way to get the correct JavaFX dependencies or build config for Java 7?
Also, when building with Java 8 some unit tests fail.
The text was updated successfully, but these errors were encountered: