How 1c-company/ssl-support works
Project type and purpose
• This is an Eclipse-based extension (“1C:SSL support for 1C:EDT”) that plugs into the 1C:Enterprise Development Tools (EDT) IDE.
• It consists of multiple OSGi bundles (plugins), a feature set, a p2 update site, integration tests, and documentation modules.
• Its goal is to provide content-assist, hyperlinked navigation, and on-the-fly type computation for the 1C BSL (Business-specific Language) libraries in the IDE.
File structure
• Top-level Maven aggregation pom.xml orchestrates submodules under directories:
• bom (Bill of Materials)
• bundles (three core OSGi plugins: com.e1c.ssl.ui, com.e1c.ssl.bsl, com.e1c.ssl.bsl.ui)
• features (feature descriptors for p2 packaging)
• repositories (p2 repository definitions)
• targets (target platform definitions)
• tests (integration tests for the BSL plugin)
• docs (documentation site sources)
• Each “bundle” folder contains an Eclipse .project, META-INF/MANIFEST.MF, plugin.xml, source code under src/com/e1c/…, and a pom.xml.
• CI/CD workflows and release pipelines are defined under .github/workflows.
• The p2 repository and features directory generate the installable update site.
Extract architectural insights from the README
• The extension is delivered as a p2 repository of OSGi bundles and features.
• The core services compute types and provide content assist for string literals and function return types.
• The UI layer registers extension points with the EDT IDE to hook into content-assist and navigation actions.
• Type-computing logic resides in the bsl bundle; the bsl.ui bundle wires that logic into the UI.
Detail
• Major directory/module as a component.