Add Scala editor

[lresende]

See #2850 (comment) for scope

What changes were proposed in this pull request?

Add Scala editor

How was this pull request tested?

EKS deployment

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[elyra-bot]

Thanks for making a pull request to Elyra!

To try out this branch on binder, follow this link:

[kevin-bates]

These changes look good, functionally speaking. I'm not qualified to comment on the code changes.

[ptitzler]

Can you please also update the related documentation topics:

• getting_started/installation.md
• user_guide/enhanced-script-support.md
• developer_guide/release.md

[karlaspuldaro]

Will this feature be added to this PR?

[karlaspuldaro]

This is where we add the submit button to other script editors from the pipeline editor package https://github.com/elyra-ai/elyra/blob/main/packages/pipeline-editor/src/index.ts#L336

[ptitzler]

I believe there should be additional places that would require updates because file type verification is performed if one tries to drag and drop a file onto the Pipeline Editor canvas.

[lresende]

As discussed in scrum, will do the run as pipeline in another pr

[ptitzler]

Are you planning to deliver the PR in 3.11? If not, we should undo some of the doc changes to avoid the impression that Scala scripts are supported in pipelines.

[akchinSTC]

ive removed the references to scala in this section

[ptitzler]

Should we treat the Scala code editor as an optionally installable component that is only installed if the [all] or [scala-editor] runtime extra was specified? As is, the editor is always installed (just like the R script editor) even though there are probably many users that will never use it.

[ptitzler]

See issues with release script.

[lresende]

Should we treat the Scala code editor as an optionally installable component that is only installed if the [all] or [scala-editor] runtime extra was specified? As is, the editor is always installed (just like the R script editor) even though there are probably many users that will never use it.

I haven't given a lot of thought for this, but we could use a separate pr to do that for the different editors

[ptitzler]

The required changes to the release script are still missing as mentioned in #2850 (comment). As is, the .whl and .tar.gz files are not published for the new extension.

[akchinSTC]

As it stands right now

1. Follow Up PR : Scala editor will be installed alongside the other editors. Not going to make it an optional package until we can get a PR going with the same optional installation support that will encompass the other editors
2. Follow up PR : Add run-as-pipeline button to scala editor
3. TODO PR : Not going to create scala-editor conda package yet. Create new staged recipe later.

Ive update the list of packages to publish via @ptitzler's comment and removed references to scala in run as pipeline section

[ptitzler]

LGTM