Support inline embedded Java code
Description
Conclusion
None
0% Done
Activity
Show:

Richard Chapman November 26, 2018 at 10:41 AM
I think Major is sufficient. It's mostly coded already as of today, so raising the priority is not going to change when it ships...

Gavin Halliday November 26, 2018 at 10:20 AM
Should this be critical?

Richard Chapman November 21, 2018 at 4:16 PMEdited
There is some overlap between the Jiras...
I assume we would handle import similar to how we handle #include in c++, e.g. something like:
Would generate a file
We can play with the exact syntax to see what works best.

David Bayliss November 21, 2018 at 3:59 PM
Obviously I don't mind which issue you put which capability in
However - there is a 'per embed' element above 20981; which is the imports needed for an embed to be valid java ... you don't really want an implicit import *;

Richard Chapman November 21, 2018 at 3:16 PM
is supposed to be covering the dependency information part of the problem.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Richard ChapmanRichard ChapmanReporter
Richard ChapmanRichard ChapmanPriority
MajorCompatibility
MinorFix versions
Labels
Pull Request URL
Details
Details
Components
Assignee

Reporter

Priority
Compatibility
Minor
Fix versions
Labels
Pull Request URL
Created November 21, 2018 at 12:55 PM
Updated March 21, 2019 at 9:16 AM
Resolved November 28, 2018 at 1:55 PM
In order to facilitate integration with Java (and Spark), it would be nice if it was as easy to embed Java as it is to embed other languages such as Python, Javascript, or R.
To achieve this, it is proposed that embedded a snippet of Java should case us to automatically wrap it in whatever boilerplate is needed to create a valid java source file, then compile that into a jar that is automatically distributed with the workunit.