Channels ▼
RSS

JVM Languages

Sonatype Repository Now Straddles Java and .NET


Sonatype has extended the use of its Nexus repository manager to .NET developers this month. Now compliant with both Java components and Microsoft platform code blocks, the company hopes to win new appeal among programming shops operating heterogeneous development environments.

Nexus Professional 2.0 (to afford it its full title) works just like any other repository tool in that it targets improved collaboration and control over component usage among its core attributes. Where Sonatype aims to differentiate is in the strength of its cross platform offering so that mixed development environments can standardize on one repository manager regardless of the language or framework — be that Java, .NET, or OSGi.

Although there are other cross platform tools in this same space (Mercurial to name just one), Sonatype's USP is probably its provision of a "common infrastructure for storing, searching, and accessing internally developed packages" — which, in theory, should make it easier for developers and groups to share code and collaborate.

"Today, .NET developers and their organizations now have the ability to define their own criteria and security measures when using NuGet for component-based development," said Scott Hunter, principal program manager at Microsoft.

With Sonatype Nexus Professional 2.0, development teams can access .NET components packaged with NuGet, the extension designed to install and update third-party components into .NET projects. By using proxies of .NET repositories colocated with developers, organizations can reduce the time it takes to load a NuGet package into Visual Studio, so improving developer productivity, but also streamlining how developers share their internal components with colleagues and counterparts.

The product's new "Availability Architecture" keeps geographically distributed teams in sync by ensuring proxy repositories know when a master repository is updated to serve the latest artifacts without sacrificing performance.


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