Repository navigation
Migrate to 2025-12 and java 21 - #42
Merged
Merged
Conversation
Point the repository at palladio-target-platforms 6.0.0-SNAPSHOT with the palladio-2023-12 classifier and at repository-parent 0.11.1-SNAPSHOT.
Runtime requirement, language level and the JRE bound by the IDE are set to 21 together, so they no longer contradict each other: Bundle-RequiredExecutionEnvironment, the compliance/source/target keys in .settings/org.eclipse.jdt.core.prefs and the JRE_CONTAINER entry in .classpath. Eclipse 2023-12 already provides the JavaSE-21 execution environment, so the target platform stays untouched. This also removes the last bundles that were still pinned below 1.8.
The execute-generate-workflow profile regenerates the EMF model bundles during the build and writes Bundle-RequiredExecutionEnvironment from the genmodel's complianceLevel. Left at 17.0 it silently reverted those bundles to Java 17 on every build - which is exactly what happened to the stoex and metricspec bundles before this change.
The target definition now resolves against palladio-2024-06, and the mdsd.tools dependencies are taken from their nightly update sites instead of pinned 1.0.0 releases, so that changes there are picked up without a release first.
The target definitions pointed at the mdsd.tools nightly sites while those repositories were being restructured. All seven that produce a release are now published as 1.1.0, so the dependency is pinned to that release again. Library-ModelCompositionRefinement has no release and stays on its nightly site; ThirdParty-Library and the GMF tooling mirror are static sites that were never part of the round.
The simultaneous release moves from 2024-06 to 2025-12 and Orbit from 4.32 to 4.38. Two units have to be requested explicitly because they no longer arrive transitively: org.apache.commons.codec, which EDP2 and SimExp require directly, and commons-text, which replaces the StringEscapeUtils that commons-lang3 dropped. JUnit is pinned to the 5.14.1 line: the aggregation ships 5.x and 6.x side by side and an unpinned version would silently pull JUnit 6. The .source features of EMF Compare and the Parsley SDK left the release; the features themselves take their place. The mdsd.tools dependencies come from their 1.2.0 releases. Four target definitions in Yakindu that no target platform ever referenced are removed: they pinned Eclipse Neon, Oxygen, Photon and 2018-09 and were pure dead weight.
palladio-target-platforms 6.0.0-SNAPSHOT -> 6.0.0 and the build parent 0.11.1-SNAPSHOT -> 0.12.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.