[Oomph-Setup] Add jdt.debug configuration setup

[HannesWell]

What it does

Add jdt.debug configuration setup.
Additionally add a styled and drag&drop-able Oomph Configuration button to the main README.

Part of eclipse-platform/eclipse.platform.releng.aggregator#2430

Author checklist

• I have thoroughly tested my changes
• The change is following the coding conventions
• I have signed the Eclipse Contributor Agreement (ECA)

[HannesWell]

@jukzi or @iloveeclipse, could you please submit this as well? Thanks in advance.

[jukzi]

why is "<" encoded with lt but ">" is not gt encoded?

[HannesWell]

The Oomph-Editor is doing this. I assume it's not necessary.
It's the same for other configurations as well.

[jukzi]

Also in exiting configurations i can not read such fields:

it's illegal xml. @merks can you fix that?
I'll be AFK 2w

[merks]

The only problem I see is that these PRs need to be merged:

#533
eclipse-jdt/eclipse.jdt.ui#1710
eclipse-jdt/eclipse.jdt.core#3071

That's the reason for these three broken references:

Could you please merge those too?

---

It's normal that only up to the first newline character is shown in the properties view. The cell editor shows the whole text:

The hover also shows it nicely formatted:

As does this page:

https://www.eclipse.org/setups/installer/?url=https://raw.githubusercontent.com/eclipse-jdt/eclipse.jdt/master/org.eclipse.jdt.releng/JDTConfiguration.setup&show=true

So no, a > is not invalid XML in element content. That's why EMF does not escape them for element content:

https://github.com/eclipse-emf/org.eclipse.emf/blob/e810c433fd597d68a246cb384251214a301e871e/plugins/org.eclipse.emf.ecore.xmi/src/org/eclipse/emf/ecore/xmi/impl/XMLSaveImpl.java#L3339-L3375

But does for attribute content:

https://github.com/eclipse-emf/org.eclipse.emf/blob/e810c433fd597d68a246cb384251214a301e871e/plugins/org.eclipse.emf.ecore.xmi/src/org/eclipse/emf/ecore/xmi/impl/XMLSaveImpl.java#L3496-L3538

[jukzi]

So no, a > is not invalid XML in element content

The right angle bracket (>) may be represented using the string " > ", and MUST, [for compatibility](https://www.w3.org/TR/xml/#dt-compat), be escaped using either " > " or a character reference when it appears in the string " ]]> " in content, when that string is not marking the end of a [CDATA section](https://www.w3.org/TR/xml/#dt-cdsection).
https://www.w3.org/TR/xml/

ok, in this case it is not invalid. while in general it may be invalid. So i would always encode it to be on the valid side, but that doesn't matter for this pr.

[merks]

ok, in this case it is not invalid. while in general it may be invalid. So i would always encode it to be on the valid side, but that doesn't matter for this pr.

In general it's never invalid in element content. Moreover, EMF has done it this way for 25 years without anyone ever suggesting it should be changed. If it ain't broke, don't fix it. 😬

[HannesWell]

Thank you Jörg for submitting this!

The results look good and as expected:

And if you click it, the installer page looks good too:
https://www.eclipse.org/setups/installer/?url=https://raw.githubusercontent.com/eclipse-jdt/eclipse.jdt.debug/master/org.eclipse.jdt.debug.setup/JdtDebugConfiguration.setup&show=true

[merks]

Cool. 😎

[merks]

@jukzi

FYI, the corner cases are handled properly by EMF: