A bare <PACKAGE NAME="Developer" /> only adds the package's RELEASED plugins, so half of them (the STABLE ones) were missing and Configure showed Developer unticked. The project window wasn't configured at all. - CodeBrowser: insert ghidra/codebrowser-developer.xml, which lists the STABLE plugins explicitly, into the default CodeBrowser.tool in Public_Release.jar. - Project window: it has no default config to patch, so ship ghidra/FrontEndTool.xml in the user settings with its three Developer plugins. - Pre-creating the settings dir makes Ghidra show its user agreement; ghidra/preferences sets USER_AGREEMENT=ACCEPT, the value Ghidra writes by itself on a fresh start. Verified by closing Ghidra cleanly: it rewrites FrontEndTool.xml from the loaded plugins and kept all three Developer plugins. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9 lines
513 B
XML
9 lines
513 B
XML
<!-- Inserted at build time (see Dockerfile). The bare package adds its
|
|
RELEASED plugins; the STABLE ones must be listed explicitly. -->
|
|
<PACKAGE NAME="Developer">
|
|
<INCLUDE CLASS="ghidra.app.plugin.debug.GenerateOldLanguagePlugin" />
|
|
<INCLUDE CLASS="ghidra.app.plugin.debug.JavaHelpPlugin" />
|
|
<INCLUDE CLASS="ghidra.app.plugin.gui.WindowLocationPlugin" />
|
|
<INCLUDE CLASS="ghidra.feature.fid.plugin.FidDebugPlugin" />
|
|
</PACKAGE>
|