Arquillian Blog

Since we wrote this post we didn't laze around. Check our latest announcement.

The Arquillian team is proud to announce the 2.2.0 release of the ShrinkWrap Resolver component!

The most significant change since the previous release is the postponing of the settings.xml loading.
Previously, when a user wanted to specify completely different settings.xml:

Maven.configureResolver().fromFile("path/to/my_settings.xml");

During the call configureResolver() the default settings.xml was immediately loaded and later on regenerated with the given my_settings.xml. This process could in some cases cause unexpected behavior (eg. the default settings.xml was corrupted).

In this new release, the loading has been postponed to the time when:

1. the settings.xml is needed (eg. artifacts resolving)
   or
2. the resolver is configured with some specific settings.xml (eg. calling fromFile("path/to/my_settings.xml"))

So, there is no change for the user in the usage – it now just does what the user wants (ie. when some different settings.xml is specified, the default one is never loaded).

Significant additions since the last final release 2.1.1:

Gradle importer
List resolution
MavenCoordinates as output
Better cooperation of MavenImporter and IDEs
Upgrade to Aether 1.0.0.v20140518
Upgrade to Maven 3.2.5

And many other bugfixes and feature requests. For more information see the release notes of the preceding alpha releases.

Big kudos to all contributors who helped to make this stable release.

We hope that you’ll enjoy our new release and look forward to hear your feedback on the community forums.

What is ShrinkWrap Resolver?

The ShrinkWrap Resolvers project provides a Java API to obtain artifacts from a repository system. This is handy to include third party libraries available in any Maven repository in your test archive. ShrinkWrap Resolvers additionally allow you to reuse all the configuration you've already specified in the Maven build file, making packaging of an application archive much easier job.

Release details

Component	ShrinkWrap Resolver
Version	2.2.0 view tag
Release date	2015-09-16
Released by	Matous Jobanek
Compiled against	JUnit – 4.11

Published artifacts org.jboss.shrinkwrap.resolver

• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-bom pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-gradle-embedded-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-gradle-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle-embedded-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi jar javadoc pom

Release notes and resolved issues 4

Feature Request

• SHRINKRES-226 - Loading of the settings.xml configuration should be postponed

Bug

• SHRINKRES-224 - Generated artifacts from workspace are missing directory entries
• SHRINKRES-229 - Fix the javadoc to meet JDK 8 requirements
• SHRINKRES-230 - Tests in ClasspathWorkspaceReaderTestCase are failing when running in IDE

Thanks to the following list of contributors: Matous Jobanek, Olivier Spieser, Michal Matloka, Karel Piwko