Many of you are developing with light-weight servlet containers such as Jetty or Tomcat.  While these platforms lend themselves to rapid application development, they often force you to forgo some of the benefits of running in a larger application server.  One of the most challenging tasks is finding a way to integrate a transaction manager into a simpler servlet-container without adding too much complexity to your configuration.  In this post, Stephen Connolly demonstrates how configure the maven-jetty-plugin to start Jetty with OpenEJB.

To read the full post, click here.

 

We found this great blog post about the top 10 myths surrounding Maven.  The article offers in depth analysis of these Maven myths, a thorough debunking of each one, and constructive ways to take action if you still disagree.  To read the full article, click here.

Maven has been a real joy for me. It could be the simple fact that I can move from colleague to colleague’s project without wondering what ant tasks are available or where the files are. It could be the fact I don’t have to configure IDE’s anymore, not even for downloading sources. It could be some of my favorite plug-ins. Maybe it’s the 250,739 artifacts that are available in three lines of copy paste declaration. There’s a lot to love.

Thanks for the props!

 

This video demonstrates how easy it is to add dependencies using m2eclipse.    Because m2eclipse understands how to interact with a repository index, it can quickly locate a dependency by class name or by GAV coordinate.    Don’t know which artifact contains a particular class?   Just start writing code and use an Eclipse Quick Fix to search all Maven repositories for an artifact that contains a particular class.    Want to inspect and browse a Maven repository? Don’t use a web browser.  Use the built-in dependency search feature in m2eclipse.

 

Much has been said in the blogosphere about the differences between Maven and Ant.  Lines have been drawn between tech bloggers, and one thing has become clear; people love to argue about Maven versus Ant.  And we love the debate.  Constructive criticism is what keeps companies fresh, and products user-friendly.  Here is another chapter in the debate:

Standardization of build systems is one of the main benefits that Maven brought to the world. If you know one Maven project, you can switch to any other project built with Maven and feel comfortable immediately. This increases productivity, both personally and for your company, which is one of the reasons more and more companies switch over from Ant to Maven.

To read the full post, click here.

 

Sonatype is excited to announce that p2 is one of the finalists for the Eclipse Community Award!  P2 is a finalist in the ‘most open project’ category.  The winners will be announced at EclipseCon 2010 on March 22.  Sonatype’s Pascal Rapicault was also nominated in the ‘Top Committer’ category.  To watch a screencast of Sonatype’s p2 support, click here.

 

Register today for the Sonatype Maven Meetup being held this April.  The meetup will take place in Philadelphia at the Sheraton Society Hill, on April 7, 2010.

The meetup will focus on development infrastructure technologies, offering talks and workshops led by core contributors and package maintainers.

Sessions in two tracks will cover tools such as the Apache Maven build and release manager, Hudson continuous integration engine, Nexus repository manager, Sonar quality server and other technologies widely used by software developers around the world.

Register for the Sonatype Maven Meetup at www.sonatype.com/meetup2010

 

Today Charles Nutter, core member of JRuby, discussed two projects that integrate JRuby and Maven, and the implications of this interoperability.  The first is a prototype Maven server that will make any Java library installable as a gem.

Let me repeat that: ANY Java library in the world, installable as a gem. This means you can also use Maven artifacts as dependencies in regular Ruby gems, and it additionally means we won’t have to re-release jar files into their own duplicate gems on the standard repositories. It’s very exciting.

The second project is Polyglot Maven, which was started by Jason van Zyl and the folks at Sonatype.

That project intends to provide standard DSLs for popular JVM languages, allowing you to use those languages in place of the XML-based POM files so many people hate.

To read the entire interview with JRuby’s Charles Nutter, click here.

 

Word keeps spreading about our Java.net Maven Rescue Misson taking place Friday March 5, 2010.  And Maven users and non-Maven users alike are excited to take advantage of the offer.  If you’re not sure whether to take up Sonatype on their offer to migrate your Maven Repository infrastructure over to our hosted Nexus OSS instance, this post offers some great insight.

Providing free maven repos I think has a lot of benefits and not just for maven users. For example, this should benefit all dependency management tools that are built on top of maven repos… Another benefit is being able to standardize on maven repositories, hopefully preventing users from searching where they can find your artifacts. I’ve wasted a lot of time in the past trying to find valid repositories where I could find artifacts for a project I was wanting to use.

To read the full post, click here.

 

Intuit has streamlined its software development lifecycle by migrating to Maven and Nexus Professional.

Intuit, Inc. provides business and financial management solutions for small and medium sized businesses, financial institutions, consumers, and accounting professionals in the United States, Canada, and the United Kingdom.

The company offers QuickBooks financial and business management software and services, technical support, financial supplies, and Web site design and hosting services for small businesses; and small business payroll products and services, as well as merchant services comprising credit and debit card processing, electronic check conversion, and automated clearing house services.

It also provides TurboTax income tax preparation products and services for consumers and small business owners; Lacerte and ProSeries professional tax products and services, and QuickBooks Premier Accountant Edition and the QuickBooks ProAdvisor Program for accounting professionals. In addition, Intuit offers outsourced online banking services for banks and credit unions, as well as Quicken personal finance products and services, Intuit real estate solutions. The company was founded in 1983 and is headquartered in Mountain View, California.

Business problem:

Prior to implementing Maven and Nexus Professional, Java projects were mostly built with Ant, and sometimes by the IDE. After migrating builds to Maven, software artifacts were not managed using Nexus.  The artifacts were not reliably available and builds were not always reliable.

Intuit employs a software development methodology where geographically distributed teams write, test, and then publish components for local or distributed use.  Open source components are also used within the company.  In order to support this approach, the company needed a new way to reliably share components.  Intuit was looking to improve developer productivity while maintaining control over what third-party artifacts were used by the teams.

Why Maven and Nexus Professional?

In their search for a new solution, Intuit engineers saw that open source artifacts are much easier to manage and build with Maven. They were further convinced by the fact that many open source projects are using Maven.

Intuit chose Nexus Professional based on its higher performance compared to competing products, as well as P2 repository support, staging, and procurement features. Sonatype’s Nexus Professional support was also very important.

Results:

After a transition period following the implementation of Maven, Intuit has begun to standardize company-wide on Maven for building its software. Teams are benefiting from seamless integration with systems such as Sonar, Hudson, and many other tools currently in use inside the company.

Nexus Professional has been providing a very stable platform for repository management of internal and third-party artifacts. Several business units have successfully utilized the staging feature, allowing the teams to be instantly in sync on internally developed artifacts, and virtually eliminating mis-communication about which components should be used for which projects.

By switching to Maven and Nexus Professional, Intuit was able to build a complete Continuous Integration system including testing and static analysis tools with a minimum of effort.

Core benefits of migrating to Maven and Nexus:

• Ability to coordinate component reuse between multiple teams
• Ability to deal with high-complexity projects
• Increased team productivity
• Increased stability of the development infrastructure

Company Profile:

• Intuit Inc., Mountain View, CA
• Web address: www.intuit.com
• Company size: Approx 5000 employees – Number of developers: Approx. 500
• Software used in the environment: Hudson, Sonar, Clover, Perforce, JBoss, Oracle, and others

 

This week DZone chatted with Sonatype’s Jason van Zyl about the upcoming Maven Rescue Mission.  They discuss why Java.net’s Maven infrastructure is causing developers so many headaches, how Nexus OSS can save you from Java.net hell, and the final straw that became the catalyst for the Maven Rescue Mission on March 5.

The Maven repository infrastructure at Java.net is very difficult for a Maven-based project to use…The Nexus OSS infrastructure provides the easiest way for Maven-based projects to publish their artifacts.

To read the full DZone article, click here.

 

The latest edition of Repository Management with Nexus, Edition 2.1, has been released. This edition includes new content about Nexus 1.5.0 Open Source and Enterprise LDAP. Edition 2.1 also contains almost 100 corrections which were driven by the community.

• Read the Book for FREE online,
• Download the Repository Managment with Nexus PDF,
• Purchase a Printed Copy for $20.06 from Lulu, or
• Read the Book on Scribd

The following changes were introduced in Edition 2.1 in February, 2010:

• Updated content for the Nexus 1.5.0 Release
  • Updated Nexus Open Source version to 1.5.0 (NXBOOK-433)
  • Updated Nexus Professional version to 1.5.0.2 (NXBOOK-434)
  • Added information about the Open Source LDAP Feature to Section 1.2.1, “Nexus Open Source Features”. (NXBOOK-435)
  • Added information about the Enterprise LDAP Feature to Section 1.3.1, “Nexus Professional Features”. (NXBOOK-437)
  • Updated Section 1.4, “Choosing a Nexus Edition” to reflect the LDAP feature changes.
  • Updated Chapter 2, Repository Management to reflect the LDAP feature changes.
  • Added Section 7.6, “Enterprise LDAP Support”. (NXBOOK-436)
• Througout Chapter 8, Nexus Procurement Suite there are alternating references to a strategy known both as the “Secured Development Repository” and the “Procured Development Repository”. To avoid confusion the strategy is now referred to as “Procured Development Repository”. (NXBOOK-420)
• Removed the Nexus Plugins chapter. This chapter was incomplete and incorrect. Until we can commit to a larger survey of available Nexus plugin, it makes sense to remove this chapter. (NXBOOK-445)
• Updated Figure 1.1, “Sonatype Nexus Feature Matrix” to include Nexus 1.5.0 features. (NXBOOK-421)
• Section 3.4, “Running Nexus” contained a reference to a login dialog figure that has been removed. This reference has been removed. (NXBOOK-402)
• Section 7.3, “Connection and Authentication” stated that the LDAP authentication user had to be a user with administrative rights to the LDAP server. This is incorrect, copy updated to state that the user simply needs to have privileges to read all users and groups. (NXBOOK-31)
• Added labels to figures in Chapter 16, Artifact Bundles. All of these figures were missing proper labels. (NXBOOK-328)
• Updated the copyright year.
• Numerous updates to Chapter 9, Nexus Staging Suite
  • Rewrote portions of Section 9.1, “Introduction” to make the introduction more straightforward for new users. (NXBOOK-423)
  • Changed the “Installing Staging Suite” section to Section 9.2, “Using the Nexus Staging Suite”. Since the Nexus Staging Suite is bundled with Nexus Professional, it doesn’t make any sense to provide installation instructions. (NXBOOK-425)
  • Made sure to reference that target created in Section 9.3.1, “Configuring a Staging Target” from Section 9.3.2, “Configuring Staging Profiles”. In the previous edition, we made no mention of the Sonatype Sample target when creating the staging profile. This change makes the section more direct, you define profiles to be activated when an artifact matches a repository target. (NXBOOK-429)
  • Reordered the sections in Section 9.3, “Configuring Staging Profiles”. The previous edition started with role assignment. This doesn’t make sense in the workflow of defining a Staging repository because the act of defining a Staging Profile creates several new roles. (NXBOOK-428)
  • Added “Close Staging Repository Rulesets” to Section 9.3.2, “Configuring Staging Profiles”. (NXBOOK-430)
  • Fixed a label problem with Figure 9.3, “Enterprise Menu after Staging Suite Installation”. (NXBOOK-427)
  • Added some lists to Section 9.3.3, “Adding the Staging Deployer Role” to clarify the staging roles. The previous edition lacked an explicit list of the roles created by a Staging Profile. (NXBOOK-426)
• Fix typos through the book (most issues subtasks of NXBOOK-256 and NXBOOK-220)
  • Fix a typo in Section 5.7, “Log Files and Configuration”. “Logs and Config Files is only visible” is now “The Logs and Config Files link is only visible” (NXBOOK-258)
  • Fixed a typo in Section 2.1.3, “Getting Control of Dependencies”. “producing a application” is now “producing an application”. (NXBOOK-255)
  • Fixed a typo in Section 9.6.2, “Defining Rulesets for Promotion”. “Nexus Professional was check” is now “Nexus Professional will check”. (NXBOOK-416)
  • Fixed a spelling error in Section 9.5, “Uploading a Staged Deployment in Nexus”. “expose a button labelled” is now “expose a button labeled”. (NXBOOK-259)
  • Fixed a typo in Section 5.5, “Uploading Artifacts”. “When you build makes use” is now “When your build makes use”. (NXBOOK-260)
  • Fixed a typo in Section C.3, “Configuring Nexus to Serve SSL”. “this instructions” is now “these instructions”. (NXBOOK-261)
  • Fixed a typo in Section C.3, “Configuring Nexus to Serve SSL”. “But, Jetty can easily” is now “Jetty can also”. (NXBOOK-262)
  • Fixed a typo in Section A.7, “Configuring Artifactory Clients to Use Nexus”. “identifer” is now “identifier”. (NXBOOK-264)
  • Fixed a typo in Section A.5.2, “Configuring Artifactory Repository Imports”. “Repostiores” is now “Repositories”. (NXBOOK-265)
  • Fixed a sentence structure issue in Section A.1, “Introduction”. “using a web application which exposes” is now “using a web application, exposing”. (NXBOOK-266)
  • Fixed a sentence structure issue in Section 5.5, “Uploading Artifacts”. Fixed a spelling error in same section. “labelled” is now “labeled”. (NXBOOK-269)
  • Fixed a few typos in Section 9.3.2, “Configuring Staging Profiles”. (NXBOOK-271)
  • Fixed a spelling error “LDAP Integeration” is now “LDAP Integration” in Figure 1.1, “Sonatype Nexus Feature Matrix”. (NXBOOK-408)
  • Fixed typos in Section 1.3.1, “Nexus Professional Features”.
    • “integration” changed to “integrate”. (NXBOOK-403)
    • “to sign up for [an] account” (NXBOOK-404)
  • Fixed a typo in Section 2.3, “What is a Repository Manager”. “Once you start [to] rely…” (NXBOOK-405)
  • Fixed a typo in Section 3.2.2, “Installing Nexus Open Source”: “whenever” -> “wherever” (NXBOOK-406)
  • Fixed an error in Section 3.4, “Running Nexus”. Section was pointing to the wrong location for wrapper.log. (NXBOOK-401)
  • Fixed a mispelling in Section 18.3, “Creating a Complex Plugin”. “ApplicaitonEventMulticaster” -> “ApplicationEventMulticaster” (NXBOOK-365)
  • Fixed a spelling error in Section 8.1, “Introduction”. “funnelled” is now “funneled”. (NXBOOK-274)
  • Fixed a typo in Section 7.5.2, “Mapping External Roles to Nexus Roles”. “bring a up” is now “bring up”. (NXBOOK-275)
  • Fixed a typo in Section 7.5.1, “Mapping Nexus Roles for External Users”. “To explore these two sets of user[s]” (NXBOOK-278)
  • Fixed a typo in the title of Table 7.9, “Group Element Mapping Configuration for posixGroup”. “posixAccount” should be “posixGroup” (NXBOOK-31)
  • Reworded the initial sentence of Section 2.2.3, “Addressing Resources in a Repository” for clarity. (NXBOOK-252)
  • Reworded portions of Section 2.2.4, “The Central Maven Repository”. (NXBOOK-252)
  • Removed the first sentence of Section 2.4.3, “Ease the Burden on Central”. (NXBOOK-249)
  • Fixed a spelling error in Section 2.4.6, “Deploy 3rd Party Artifacts”. “hand-crafting” is now “handcrafting” (NXBOOK-248)
  • Fixed a that/which in Section 2.4.6, “Deploy 3rd Party Artifacts”. (NXBOOK-248)
  • Added a hyphen to “developer-managed” in Section 2.5.1, “Stage Zero: Before Using a Repository Manager”. (NXBOOK-247)
  • Fixed several sentence structure issues in Section 2.5.1, “Stage Zero: Before Using a Repository Manager”, Section 2.5.1, “Stage Zero: Before Using a Repository Manager”, and Section 2.5.3, “Stage Two: Hosting a Repository Manager”. (NXBOOK-246)
  • Fixed a sentence structure issue in Section 2.5.3, “Stage Two: Hosting a Repository Manager”. (NXBOOK-245)
  • Fixed sentence structure issues in Section 2.5.4, “Stage Three: Continuous Collaboration” and Section 2.5.5, “Stage Four: Lifecycle Integration”. (NXBOOK-244 and NXBOOK-243)
  • Fixed a sentence structure issue in Section 3.2.2, “Installing Nexus Open Source”. (NXBOOK-239)
  • Fixed a that/which issue in Section 3.2.3, “Installing Nexus Professional”. (NXBOOK-238)
  • Fixed a typo in Section 18.1.2, “Nexus Extension Points”. “descriptor with is” is now “descriptor which is”. (NXBOOK-363)

The following individuals provided valuable feedback resulting in fixes and changes in Edition 2.1:

• Anders Hammar
• Brian Demers

 

Devnexus 2010 is the annual Professional Developer Conference, and is being held in Atlanta on March 8 and 9.  Sonatype’s Jason van Zyl will be in Atlanta on March 8 to give a presentation on Maven 3 and Next Generation Development Infrastructure.  The presentation will cover the future of Maven, Maven 3, the release of m2eclipse 1.0, and the move towards a standardized development stack that includes tools like Maven, Hudson, m2eclipse, and Nexus.

This discussion will focus not only on the tools individually, but how they can work together to create a best practices approach to building and delivering your software in your organization.

For more information on Devnexus 2010 visit the conference website.  Devnexus 2010 is sponsored by the Atlanta Java User Group.

 

Parleys.com has just published my “Maven 3: Reloaded” presentation from Devoxx ‘09. In this presentation, I put our current focus on Maven 3 in context and talk about some of the upcoming technologies like Polyglot Maven and Maven Shell. In this video you’ll see me demonstrate POM translation from XML to Groovy, discuss the ways in which Maven 3 changes allow m2eclipse to embed Maven, and some of the work we’ve done in Tycho to provide a path for OSGi developers.

You watch this embedded video, or watch the presentation over on the Parleys.com site.

Note: To switch between the slides and the video of me talking, click on the smaller video in the upper right-hand of this video embed.

 

Good news travels fast, and word about our Java.net Maven Repository Rescue Mission is getting a positive response.

I guess we can say the java.net repository is a little broken…But there is a good news! Sonatype is opening it’s Nexus OSS instance to all java.net projects.

This blog entry details a few examples of the headaches that the Java.net repository has caused.  You can read the full blog entry here.  As promised, on March 5th we will start servicing all requests to switch Java.net projects over from their Maven Repository infrastructure to our Nexus OSS Instance.

If you use Maven and deploy on java.net, I think that’s a good opportunity to save pain and improve your release cycle!  

There are numerous problems with the Maven repositories on Java.net, and individual projects are being penalized for poor development infrastructure at Java.net. We hear no end of complaints about the poor quality of Maven Repositories at Java.net: mixing of Maven 1 and Maven 2 repositories, the mixing of releases and snapshots, lack of javadocs, sources, signatures, bad project metadata, and general inability of Java.net to provide any coherent means of delivering valid repository content to the Maven community.

This is not a problem with any particular project at Java.net, it’s the infrastructure provided by Java.net that isn’t up to par. You need to provide a decent Maven repository infrastructure for projects to deploy their content to, and you need to provide instructions about best practices on how accomplish this properly. Java.net has done neither, so I figured instead of continuing to complain –and continuing to field the complaints of Maven users– I’m going to do something about it.

On March 5th, 2010 Juven Xu and Marvin Froeder from Sonatype will start servicing any and all requests from Java.net projects to migrate their Maven Repository infrastructure over to our hosted Nexus OSS instance. We will, of course, continue to service requests after March 5th, but March 5th will be set aside to specifically help Java.net projects get switched over and tested.

We generally ask that projects interested in our OSS hosting service familiarize themselves with our guide for OSS Repository Hosting. If you follow the guide and make your request we will process the requests on a first come, first serve basis on March 5th. We’ve helped close to 100 projects now and we’d love to help the projects at Java.net!

 

Manfed Moser, the author of the newly released Android chapter in Maven: The Complete Reference, wrote a very quick step-by-step set of instructions for people interested in contributing to the Maven book. Read the whole post here: http://www.simpligility.com/2010/02/how-to-contribute-to-the-maven-books/

Here’s an excerpt:

The first thing you will have to do is get the source code – after all the books are open source licensed and freely available to anyone. The books are found on github at http://github.com/sonatype/ and in the case of the reference book at http://github.com/sonatype/maven-reference-en. With the excellent help on github you can just fork the repository and get your own copy going locally. My copy for example is at http://github.com/mosabua/maven-reference-en

Now thanks to the power of Maven and its conventions you get the book created as HTML website and PDF document by running, surprise, mvn clean install  

The latest edition of Maven: The Complete Reference, Edition 0.4, has been released. This edition updates the Flexmojos chapter to the latest FlexMojos 3.5.0 release and refreshes information about Flexmojos archetypes. We added an initial version of a chapter by Manfred Moser that walks through the process of using Maven to build Android applications. In addition to that we fixed some minor issues throughout the book that had been reported by the community.

• Read the Book for FREE online,
• Download the Maven: The Complete Reference PDF,
• Purchase a Printed Copy for $19.86 from Lulu, or
• Read the Book on Scribd

A full list of changes in Edition 0.4:

• Added a new chapter: Chapter 14, Android Application Development with Maven. (MVNREF-135)
• Updated the Flexmojos version to 3.5.0 in Chapter 13, Developing with Flexmojos. (MVNREF-127)
  • Added some clarification to Section 13.2.1, “Referencing a Repository with the Flex Framework” that suggests adding the flexmojos repository to an existing Nexus installation.
  • Reorganized Section 13.2.1.2, “Proxying Sonatype’s Flexmojos Repository with Nexus”. Added level four headings to group content into more easily understood chunks with respect to Nexus configuration.
  • Fixed minor typos throughout Chapter 13, Developing with Flexmojos.
  • Updated all of the Flexmojos Maven Archetypes with most recent pom.xml content. Changes affected Section 13.3.1, “Creating a Flex Library”, Section 13.3.2, “Creating a Flex Application”, and Section 13.3.3, “Creating a Multi-module Project: Web Application with a Flex Dependency”.
  • Removed the warnings in the multi-module project exampe in Section 13.3.3, “Creating a Multi-module Project: Web Application with a Flex Dependency”. There used to be a problem with the archetype module dependencies, this has been fixed in the recent Flexmojos releases.
• Section 5.5.1, “Common Environments” was incorrect. The property defined in ~/.m2/settings.xml was not activating the profile defined in a project’s POM. This seciton has been corrected. (MVNREF-124)
• Fixed a code overflow in Section 7.1.4, “Setting Execution Specific Parameters”. (MVNREF-118)
• Fixed unescaped property references and a code overflow in Example 3.1, “The Super POM”. (MVNREF-117)

The following contributors provided invaluable feedback and contributions:

• Emmanuel Hugonnet provided the issue report that prompted the update of the Flexmojos chapter to version 3.5.0.
• Benjamin Bentmann reported an inconsistency in Section 5.5.1, “Common Environments”.
• Manfred Moser was added as a primary author for contributing Chapter 14, Android Application Development with Maven.

 

The following demonstration video was shown in the Sonatype booth at last month’s Jfokus 2010 in Stockholm, Sweden. This video provides a quick walkthrough of the major features in Nexus Scheduled Jobs.

Highlights of this demonstration:

Time (M:SS) Note 0:29 Managing Nexus Scheduled Jobs 0:32 Creating a New Scheduled Job 0:58 Configuring Task Settings 1:23 Job Email Notification 1:32 Configuring a Job’s Schedule 1:32 Configuring a Job’s Schedule 1:55 Manual Execution of a Task 2:15 Available Task Types 2:31 Schedule Recurrence Options 2:45 Scheduling a Job using a CRON Expression 2:59 Monthly Scheduling 3:03 Weekly Scheduling 3:13 Daily Scheduling 3:21 Hourly Scheduling 3:31 Task Type: Scheduled Backups 3:39 Task Type: Scheduled Remote Index Downloads 3:49 Task Type: Emptying the Trash 3:57 Task Type: Evicting Unused Proxy Artifacts 4:05 Task Type: Expiring Repository Caches 4:10 Task Type: Publishing Indexes 4:19 Task Type: Purging Nexus Timeline 4:25 Task Type: Rebuilding Maven Metadata 4:29 Task Type: Reindexing Repositories 4:37 Task Type: Removing Snapshots 4:43 Task Type: Synchronizing Shadow Repository 4:49 Task Type: Mirror an Eclipse Update Site  

Welcome to the roundup of blog posts that mention Nexus, Maven, and other projects that Sonatype developers contribute to.

DevDanke: Create an Executable Jar with Maven
“There are several ways to make an executable jar with Maven. Two popular ways are to use the maven-jar-plugin or use the maven-assembly-plugin. Each has pros and cons.”
By Dan, on February 18, 2009

IBM DeveloperWorks: Build better Web applications with Google Sitebricks: Create a sample Java Web application using Maven, Sitebricks, and Guice
“Sitebricks, which is still in beta, is a new Java™ Web application framework. You might wonder, “Why do I need yet another Web framework?” With Google Sitebricks you can rapidly build a Web application that can be maintained, or worked on, by others. Sitebricks is built on top of Guice. It expands and extends many of the principles of Guice to the Web. Like Guice, it makes aggressive use of annotations to keep configuration as part of the code. You will not have to create or edit a lot of XML files to use Guice. Instead, Sitebricks lets you create Web applications while writing a lot less code. The code you write will be straightforward. You can look at Sitebricks code and quickly understand what’s going on. Sitebricks does not compromise type safety or performance.”
By Michael Galpin, Software architect, eBay, on 16 Feb 2010

Bram’s Braindump:Howto: soapUI integration tests with Maven
“Running soapUI tests with maven is surprisingly easy, all it requires is a few simple steps. This howto will walk you through deploying your web project in an embedded container and running the soapUI tests in the integration test phase.”
By Bram, on 15 February 2010

Java Evangelist John Yeary’s Blog: Introduction to Apache Maven Presentation
“This is an Introduction to Apache Maven presentation that I gave at the Greenville Java Users Group on the 11th of February. It covers the basics of installing and configuring Apache Maven. It also demonstrates creating three projects from relatively simple to a more complex Apache MyFaces and Facelets example. I also demonstrate the power of using the Jetty plugin to deploy and test our application. Finally I create a project site which contains information gathered from the pom.xml and project files including any unit testing.”
By John Yeary, on February 14, 2010

 

The following demonstration video was displayed in the Sonatype booth at last month’s Jfokus 2010 in Stockholm, Sweden. This video provides a quick walk through of the System Feed and Log file UI available in Nexus.

Hightlights of this video:

Time (M:SS) Note 0:26 Viewing System Feeds 0:37 Browsing System Changes 0:49 Accessing Nexus RSS Feeds 1:03 Viewing Nexus System Files 1:19 Tailing Log Files from the Nexus UI 1:32 Log4J Configuration 1:38 Latest Version Notification Configuration 1:44 Nexus Server Configuration 2:00 PGP Keyserver Configuration 2:08 Procurement Plugin Configuration 2:14 Security Configuration 2:34 Nexus Server configuration as XML