Channels ▼
RSS

Open Source

Actionable Control For Open Source Components


Sonatype has released the Nexus Professional 2.0 open-source repository manager. The new iteration now includes more "actionable" information about the open-source components used in any development project.

This action-centric approach is designed to provide insights into component security and licensing. The product also includes the Nexus Availability Architecture and the ability to manage both Java and .NET components from a single Nexus repository.

"Thousands of development shops rely on Nexus to reduce build times, improve collaboration, and increase control of open-source artifacts," said Jason van Zyl, CTO and founder of Sonatype. "Sonatype Nexus Professional 2.0 adds a whole new dimension to the repository market. Now development teams can know far more about the contents of their repositories with integrated security, licensing, and popularity information."

The company says that component-based development projects that consume or need to provide binary software artifacts have turned to Sonatype for an efficient, stable, and scalable system to manage their software artifacts. The new release includes branded modules like "Repository Health Awareness" — a component report to identify problematic components throughout the application development process and into production.

Later this year, Sonatype says that it will release Sonatype Insight for Nexus, a plug-in that combines real-time security and licensing information with a rules engine to enable effective governance of component usage. Combined with Sonatype Nexus Professional, this new plug-in will enable the automated management of white and black lists based on a variety of component information including license type, security vulnerabilities, and quality metrics.

With the new release, developers are promised options to customize their repositories with less effort using a simplified plug-in API, while more flexible licensing for plug-ins serves to enhance the overall plug-in ecosystem by encouraging more community contributions. The open-source version of Nexus offers summary repository health awareness data to make better decisions about artifact use during development.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video