This allows you to access the Karaf console by pressing enter after starting the repository manager with the run option. To enable the console, set karaf.startLocalConsole in bin/nexus.vmoptions to true. Alternatively you can add a specific feature via Karaf commands.īundles can be loaded via the Karaf console. The feature my-custom-feature is a Maven project that includes the desired bundles as dependencies. to add my-custom-feature to an Nexus Repository Manager OSS installation you can change to: nexus-features=nexus-oss-feature,my-custom-feature If you're using a Nexus Repo 3.14.0 or ealier, or the plugin is not availalbe in KAR format, use this procedure.Īn installation of the repository manager defines the feature it loads in $data-dir/etc/nexus.properties and additional features can be declared to be loaded there. Reference: Installing Bundles Into 3.14.0 and Earlier Note that KAR file support was added in version 3.15.0 of Nexus Repo. KAR files are like the old “plugin bundles” in Nexus Repo 2, they contain the plugin jar as well as its dependencies and a feature file that describes the plugin.Īssuming the plugin project uses :nexus-plugins as its parent then you can use the buildKar Maven profile when building the plugin to make a deployable KAR file. If the plugin bundle has been built as a KAR file you can just drop the file into $install-dir/deploy and it will be automatically unpacked and deployed.
The supported distributions are defined in the modules nexus-oss-feature and nexus-pro-feature, which are part of the internal code-base. A number of these definitions can be found in the assemblies module. The default build assembles multiple bundles into features that form the foundation of Nexus Repository Manager OSS and Nexus Repository Manager Pro. In order to have your features from your bundle available as part of the repository manager, the bundle needs to be loaded by the OSGi container.