-
Notifications
You must be signed in to change notification settings - Fork 5
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
junit:junit - J2ObjC continuous build #16
Comments
What Java libraries you are translating to C, Maven or JUnit? On Fri, Sep 25, 2015 at 10:30 PM, Bruno Bowden [email protected]
Cheers |
Hi @Tibor17, we are not manually translating anything to Objective C; we are merely setting up continuous testing that verifies JUnit can be automatically translated from Java to Objective C using our build tool j2objc-gradle with Google's j2objc translator. Also to be clear this project is not affiliated with Google. (j2objc itself is run by Google, but this project is run by @brunobowden and myself). |
It would be ideal to run a modern JVM on iOS but that isn't permitted by Quoting from Wikipedia: Java running on an iOS platform currently is outside the bounds of the iOS 3.3.2 — An Application may not itself install or launch other executable On Fri, Sep 25, 2015, 5:19 PM Advay Mengle [email protected] wrote:
|
@Tibor17 - we both agree that this shouldn't be necessary but this is the only proper way this can be done. Google's "Inbox", "Docs" and "Spreadsheet" apps on iOS all use translated java code via J2ObjC. @advayDev1 and I are both ex-Google engineers who are interested in extending the support to a wider range of libraries. |
A programmer-oriented testing framework for Java.
@stefanbirkner, @Tibor17 - FYI for you both. This is to support translation of your Java library to Objective-C such that it can be used on iOS. This bug is specifically for testing this as part of a continuous build using Google's J2ObjC conversion tool.
@advayDev1 FYI
The text was updated successfully, but these errors were encountered: