handle build issue in OSGi build code #2511
Merged
Conversation
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
mdedetrich
reviewed
Nov 17, 2025
He-Pin
reviewed
Nov 17, 2025
| } | ||
| } | ||
| private def useDefaultImportRange(version: String, packageName: String) = { | ||
| System.err.println(s"Invalid Pekko version: $version for OSGi import package versioning, defaulting to [0.0,10.0)") |
pjfanning
added a commit
to pjfanning/incubator-pekko
that referenced
this pull request
Nov 17, 2025
* handle build issue in OSGi build code * Update OSGi.scala
pjfanning
added a commit
to pjfanning/incubator-pekko
that referenced
this pull request
Nov 17, 2025
* handle build issue in OSGi build code * Update OSGi.scala
pjfanning
added a commit
that referenced
this pull request
Nov 17, 2025
pjfanning
added a commit
that referenced
this pull request
Nov 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
fixes #2509
Not having a semver version and having sbt-dynver derive versions like HEAD+20251117-1039 when the code is not under git control leads to other problems with the build but this issue breaks the build.
Other issues that we get with HEAD+20251117-1039 style versions include: