poc: build the registry from the upstream server library - #12195
Draft
gnugomez wants to merge 2 commits into
Draft
poc: build the registry from the upstream server library #12195gnugomez wants to merge 2 commits into
gnugomez wants to merge 2 commits into
Conversation
gnugomez
marked this pull request as draft
July 29, 2026 16:19
New server/ Gradle build: it consumes eclipse-openvsx/openvsx's server project as a library through a composite build over the upstream submodule (pinned to the paired branch, -PopenvsxServerPath overrides it), with upstream's RegistryApplication as main class and the Spring Boot version derived from the upstream version catalog. The Docker image builds the bootJar itself on a plain JRE base, replicating the previous upstream-derived image layout; Helm charts, ESO secrets and DEPLOYMENT_CONFIG are unchanged. runServer works like upstream's.
The org.eclipse.openvsx.eclipse code extracted upstream lands here as org.eclipsefdn.openvsx.eclipse, wired exclusively through EclipseFoundationAutoConfiguration against the upstream seams (PublisherAgreementService, OAuth2LoginHandler). Same endpoints, same ovsx.eclipse.* configuration keys; a dedicated Swagger UI group documents the relocated endpoint. Integration tests boot the merged application against Testcontainers PostgreSQL, and a negative test proves the registry stays healthy with the auto-configuration excluded. server/NOTES.md carries the full PoC write-up.
gnugomez
force-pushed
the
poc/openvsx-eclipse-module
branch
from
July 30, 2026 08:08
7db05b8 to
2c8d170
Compare
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.
This repo becomes a Spring Boot app of its own, consuming eclipse-openvsx/openvsx's server as a library (composite build over the
server/upstreamsubmodule) and contributing deployment-specific code via auto-configuration — instead of deriving our image from the upstream one.server/Gradle build: upstream'sRegistryApplicationas main class, the relocatedorg.eclipse.openvsx.eclipsecode underorg.eclipsefdn.openvsx.eclipse, registered only throughAutoConfiguration.imports. Same endpoints, sameovsx.eclipse.*keys../gradlew runServerworks like upstream's.DEPLOYMENT_CONFIGflow, Helm charts and ESO are unchanged.Paired upstream branch with the extraction seams: eclipse-openvsx/openvsx#2016.
Full write-up (seams, parity evidence, gotchas, productionizing):
server/NOTES.md.