Replace org.freemarker with org.freemarker.freemarker

[Kummallinen]

Fixes #546

This will have an impact on downstream consumers as they will now need to add their own package imports.

The target platform including the CDT feature was masking this issue earlier

[Kummallinen]

Apologies @jonahgraham I hadn't noticed the approval notification before I pushed an amendment. The amendment just adds a note to the API Changelog

[Kummallinen]

@jonahgraham Seems we can either add a filter to suppress the API error here (as both bundles contain the same packages so the API isn't actually broken) or we remove the re-export and bump the major version and make this a breaking API change.

Maybe a point for discussion on the call, do we want to make a breaking API change in the next release?

[jonahgraham]

Since we have a call today, lets discuss then - I've added to the agenda.

[jonahgraham]

Decision in the meeting was to update freemarker to be package imports and remove the require bundle + reexport. That may lead to a some rare breakages for anyone that was relying on the reexport, but otherwise updating freemarker bundle is identified as API breakage anyway. This needs a N&N/API entry or similar.

[Kummallinen]

Current draft updates all the freemarker related dependencies.

Once the main branch is ready for 11.4 changes I will also remove the re-export from the tools.templates.ui plugin currently tricky to do as every bundle shows API errors due to platform related changes.

I'll also add the N&N entry

[jonahgraham]

The API errors are tracked in #551

[Kummallinen]

@jonahgraham I think this is everything discussed in the call, but could do with another set of eyes to check I didn't miss anything.

[jonahgraham]

@Kummallinen I pushed a commit that updates all the items that depend on tools.templates to 2.0.0, I bumped the ui bundle to 2.0.0 for consistency and added an additional note to the API.

Can you look and see if that looks ok to you?

[Kummallinen]

@jonahgraham Thanks, looks ok to me