Sonatype is pleased to announce the release of Nexus 2.7.0, a major release including new features, bug fixes, and performance improvements.
Sonatype Nexus 2.7.0
New and Noteworthy
All Shipping Plugins are Installed by Default
Previous versions of Nexus Professional shipped with some plugins which were not installed by default. These were located in "$NEXUS_HOME/nexus/WEB-INF/optional-plugins", and installation required manually copying these over to the main plugin repository and restarting the server. In Nexus 2.7, all plugins are installed by default. The following plugins are affected:
* Note: The Unpack Plugin creates a special "content-compressed" REST endpoint which can be used to deploy zip files to a repository. The URL looks like this: http://localhost:8081/nexus/service/local/repositories/releases/content-compressed. The files in the zip will be unpacked and deployed individually to the repository.
New Atlassian Crowd Plugin
We have completely rewritten the Atlassian Crowd Nexus plugin. It performs better, is more reliable and depends on current Crowd REST APIs under the hood. Upgrades of your previous crowd configuration should be handled seamlessly.
The plugin is already installed by default and configuration can be accessed via Security -> Crowd in the sidebar. Refer to the Sonatype Nexus Book Crowd Chapter for more information.
The plugin has been primarily tested with Crowd 2.5.5 and 2.6.5 at shipping time. Although the Crowd REST API used should work with Crowd versions as old as 2.1, users are encouraged to use this plugin with at least the tested versions of Crowd or newer. In particular, Atlassian Crowd releases earlier than 2.5.5 are known to have severe security vulnerabilities.
If you use a https URL to access your crowd server, you can now configure an SSL: Crowd Capability to explicitly manage the trust of the SSL certificate
New Support Tools
The old automatic problem reporting feature under "help/report problem" has been replaced with a new set of support tools.
Nexus now has a System Information report to show detailed information about the configuration and runtime environment of the Nexus instance.
A new option to generate a Support ZIP which can be sent to Sonatype support has been added. This ZIP file is not encrypted so users can inspect the contents before providing it to Sonatype via a secure support site ticket at https://support.sonatype.com.
New Logging UI
The logging UI has been completely rewritten, and now allows for setting log levels for individual java packages and classes through the UI. It also has a new "mark" facility which can be used to add markers in the log. These markers help delineate where a problem was reproduced.
Note: The previous System Files feature has been removed and replaced by the new log viewer and Support Zip feature.
Authentication via Remote User HTTP Header
Nexus now supports external pre-authentication of users. An HTTP header can be configured (such as REMOTE_USER) which contains a user ID which has already been authenticated by the external system. See the book for more information.
Legacy Startup Scripts Removed
The old startup scripts (located under $NEXUS_HOME/bin/jsw/$ARCH in the installation directory) have finally been removed. These have been deprecated since Nexus 2.0. Users should use the new startup scripts introduced in Nexus 2.0, located in $NEXUS_HOME/bin (NEXUS-5781). The 'clickable' Windows batch files (*-nexus.bat) have remained, but the only use case for these are to be 'clicked' to perform a specific named action.
Work Directory is now Locked to Prevent Concurrent Access
The work directory is now locked to prevent simultaneous access by multiple Nexus instances. A
No Longer Possible to Disable Security
Previous versions of Nexus had a setting which completely disabled security. This added unnecessary complexity to the system, and this has been removed. If someone really wants to run Nexus without security this can be done by giving the anonymous user the Administrator role.
Custom Metadata is now Enabled/Disabled via Capability
In previous versions of Nexus the Custom Metadata Plugin shipped in "$NEXUS_HOME/nexus/WEB-INF/optional-plugins" because it can add additional overhead to large instances. It is now shipped in the main plugin repository. To enable it, go to "administration/capabilities" and add a new capability of type "Custom Metadata". If you were using it previously, you need to explicitly enable it after upgrade to keep using it. Note that this is a one time requirement, the setting will persist through future upgrades.
Plexus Components Deprecated
Components in Nexus have been converted to JSR-330 and use of Plexus components have been deprecated. Warnings will be logged on startup when Plexus components are detected. Custom plugins should be updated as support for use of Plexus components will be removed in future version of Nexus (NEXUS-5755).
Deprecated Legacy API
Many legacy, unused, or soon to be removed API have been marked as deprecated. These will be removed in future versions of Nexus. Custom plugins should be updated to avoid usage of deprecated API.
Nexus Staging Maven Plugin Automatic Release
A new parameter has been added to the nexus-staging-maven-plugin, "releaseAfterClose". When this is set the plugin will automatically release a staging repository after closing it provided that all staging rules (including CLM scans) have passed (NEXUS-5906).
Automatic Cleanup of old Build Promotion Repositories
Enhanced UI for Tables
Improved Capabilities UI
Numerous improvements have been made to the capabilities UI, including the ability to group capabilities by any column (particularly useful is grouping by "category"). Also, there is a new tabbed interface which cleanly separates Summary, Settings, Status, and About (NEXUS-5940).
Nexus Branding Plugin Improvement
The Nexus Branding Plugin (which allows setting a custom banner in the UI) can now be configured via capabilities UI (NEXUS-5891). To set a custom banner in Nexus 2.7 go to "Administration/Capabilities" and add in a "Branding" capability. Previous custom banners should be detected automatically on upgrade.
Mirrors Tab Removed from Proxy Repositories
The old "mirrors" feature has been removed from proxy repositories and previous settings will be ignored (NEXUS-5789). Proxy repositories that had this configured will now fetch all artifacts, poms, metadata and checksums from the remote proxy directly.
Significant Bug Fixes
|Free forum by Nabble||Edit this page|