You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8a0caf2
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: align plugin packaging with sample (#339)
Align `pluginZip` (renamed to installPlugin) task with the JetBrains
Toolbox sample's Marketplace archive structure: extension.json remains
at the archive root, while plugin resources and all shipped JARs live
under <plugin-id>/ and <plugin-id>/lib/. This follows the sample's
packaging convention, keeping the manifest at the archive root and
grouping plugin files beneath the plugin ID.
dependencies.json are also generated at build time from the full
dependency-license report. The generated metadata is filtered against
the resolved `runtimeClasspath`, so it includes every bundled direct and
transitive library while excluding compile-only Toolbox APIs and other
artifacts that are not shipped. Use the generated file for both local
installation and ZIP packaging.
Also added ZIP validation before publishing and after direct packaging.
It verifies the manifest and resource layout, expected plugin and
runtime JARs, JAR placement under <plugin-id>/lib/, and that
Toolbox-provided dependencies are not bundled. In addition I renamed
some of the build tasks to `generateExtensionJson`, `installPlugin`, and
`packagePlugin` to match the JetBrains Toolbox sample. Remove the
redundant `pluginPrettyZip` task, and update the README and CI build
workflow to use the new task names.
0 commit comments