Repository Management with Nexus
Chapter 21. Developing Nexus Plugins
- 21.1. Nexus Plugins
- 21.2. Nexus Extension Points
- 21.3. Nexus Plugin Extension Points
-
- 21.3.1. Nexus Plugin Extension
- 21.3.2. Nexus Index HTML Customizer
- 21.3.3. Static Plugin Resources
- 21.3.4. Plugin Templates
- 21.3.5. Event Inspectors
- 21.3.6. Content Generators
- 21.3.7. Content Classes
- 21.3.8. Storage Implementations
- 21.3.9. Repository Customization
- 21.3.10. Item and File Inspectors
- 21.3.11. Nexus Feeds
- 21.3.12. Nexus Tasks and Task Configuration
- 21.3.13. Application Customization
- 21.3.14. Request Processing
- 21.4. Using the Nexus Plugin Archetype
- 21.5. Set the Target Nexus Version
- 21.6. Building a Nexus Plugin Project
- 21.7. Creating a Complex Plugin
- 21.8. Nexus Plugin Descriptor Maven Plugin
- 21.9. The Nexus Plugin Descriptor
- 21.10. Defining Custom Repository Types
Among the many benefits of using an technology with an open source core is the ability to customize behaviour and create extensions. To this end, Sonatype has spent a great deal of time designing an intuitive Plugin API that will allow you to take Nexus where you need it to go. This chapter summarizes some of these extension points and presents a walk through of how you would start to develop your own Nexus plugins.
Our community has already created a number of compelling and useful plugins, some of which have been integrated into the set of plugins that are distributed with both Nexus Open Source and Nexus Professional. Sonatype tried to make the Plugin API as lightweight and extensible as possible with the following goals in mind:
- Providing a clear set of extension points for plugin developers
- Providing isolated plugin classpaths to avoid compatibility issues between plugins and to prevent a plugin from disturbing another, unrelated part of Nexus.
- Giving developers the ability to load and unload Nexus plugins at runtime