Return the language server to a snapshot version after 0.1.0 - #9
Merged
Conversation
0.1.0 is released and tagged, so main goes back to a development version. The release commit had to carry a plain 0.1.0 with no OSGi qualifier, which makes every local rebuild produce a byte-different jar at an identical p2 bundle version — a cache cannot tell them apart. Restoring 0.2.0-SNAPSHOT/0.2.0.qualifier puts the build timestamp back in the bundle name, so p2 and Eclipse see each rebuild as new. The aggregator moves with the server, as it did on the way up, taking the extension's parent reference with it. osate-cli and the extension stay at 0.1.0 on purpose: rpm forbids '-' in a version and VS Code extension versions must stay major.minor.patch, so both keep a plain release version in the tree and move it only when they release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
ls-v0.1.0,vscode-v0.1.0-pre, andosate-cli-v0.1.0are all released, somaingoes back to a development version.The release commit had to carry a plain
0.1.0with no OSGi qualifier — Tychorequires exact Maven/OSGi equality for a release version. The side effect is that
every local rebuild produces a byte-different jar at an identical p2 bundle
version, which a p2 cache cannot distinguish. Restoring
0.2.0-SNAPSHOT/0.2.0.qualifierputs the build timestamp back in the bundlename so each rebuild looks new.
The aggregator moves with the server, as it did on the way up, and carries the
extension's parent reference with it.
osate-cliand the extension deliberately stay at0.1.0: rpm forbids-in aversion and VS Code extension versions must stay
major.minor.patch, so both keepa plain release version in the tree and move it only when they release. This is
now written down in
RELEASING.md.Verification
Local
mvn -f aadl-language-server/pom.xml clean verify -Dtycho.localArtifacts=ignorepasses and produces
org.osate.aadl.ls_0.2.0.v20260902-1649.jar— thetimestamp qualifier is back.
🤖 Generated with Claude Code