In Nexus 1.6, we reintroduced a useful little feature that had been available in early 1.0 betas: The ability to have Nexus auto block proxies that are unreachable. What’s improved in this version is the ability to control this feature and the fact that it will auto unblock the repo once it becomes reachable again.
Whenever an artifact is downloaded from a proxy repository, it is automatically cached locally and used to serve subsequent requests. Nexus will continue to serve the artifact until it expires based on the configuration (release artifact typically never expire).
When new artifacts are being requested that Nexus has never seen before, it will look in the proxies to locate it (this behavior can be optimized with routing rules). If the remote request times out, Nexus by default will check two more times before giving up. This is usually enough to handle transient network glitches. If however, the repository is down for an extended period of time, all these retries can back up the connections and slow down over all performance. This is where the auto block comes in.
If you take testing seriously as I do, you most likely know test code coverage tools. And in the Flex Universe the de facto standard is Flex Cover. Now let’s be honest here, the tool does the job but it isn’t simple. Using it requires a special compiler to run code on Flex projects, which is the main reason why test code coverage never got into Flexmojos. The available tool was too complex to use, and so I never gave it any serious thought.
Since day one, Flexmojos has tried to follow the KISS philosophy (Keep It Simple
Stupid Smartguy). With that in mind, Flexmojos is proud to announce state of the art test code coverage support.
This blog post is a bit out of date, but you can see the latest Guide here.
The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. While there is still important work to be done on Maven 3, the project has successfully transitioned form alpha to beta. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project.
You can read more here:
Downloads of source and binary distributions are listed in our download section:
A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x:
If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list:
The Spring 2010 edition of the Sonatype newsletter is now available! Read all about Nexus 1.6 – a new release for both Nexus Open Source and Nexus Professional – and the changes that we’ve made to our repository manager. In this edition of the newsletter you can also watch the latest m2eclipse videos, view presentations from Sonatype’s Maven Meetup in Philadelphia, and learn how to find out about product releases and announcements the minute they break.
In this issue, you can also learn more about Sonatype’s instructor-led online training courses covering Maven and the design of efficient software development infrastructure. These classes are led by world-class experts in the field and have become the premier source of education for companies deploying Maven-based infrastructure.
To continue reading, click here.