ShrinkWrap Resolver 3.0.0 Released
Since we wrote this post we didn't laze around. Check our latest announcement.
The Arquillian team is proud to announce the 3.0.0 release of the ShrinkWrap Resolver component!
In the final release of ShrinkWrap Resolver 3.0.0, we are introducing you one new feature into the EmbeddedMaven logic.
Maven build invocation command & Logging
In the previous releases, there was no easy way to get the DEBUG log from the Maven Invoker tool, including the command that is used for Maven build invocation.
In this release, we are introducing a method setDebugLoggerLevel()
that sets the threshold of the InvokerLogger to DEBUG level. An example of the usage is:
EmbeddedMaven.forProject("path/to/pom.xml").setDebugLoggerLevel()
When it is set, then in the very beginning of the debug log, there is also contained the command that is used for the Maven build invocation. That will help you with debugging your potential problematic Maven builds.
Apart from this feature, you can find also several improvements, component upgrades and a lot of bug fixes there. For more information, check the release notes and resolved issues listed at the end of this announcement.
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 | 3.0.0 view tag |
Release date | 2017-11-09 |
Released by | Matous Jobanek |
Compiled against |
|
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-spi jar javadoc pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-depchain pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven 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-api-maven-embedded jar javadoc pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven-embedded jar javadoc pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle jar javadoc pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-gradle-embedded-archive jar javadoc pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-gradle-depchain pom
- org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle-embedded-archive jar javadoc pom
Release notes and resolved issues 6
- Component Upgrade
-
- SHRINKRES-277 - Upgrade to maven-invoker 3.0.0
- SHRINKRES-278 - Update Spacelift to 1.0.2 & AssertJ to 3.8.0
- SHRINKRES-280 - Update Gradle Tooling API to 4.0.1
- Enhancement
-
- SHRINKRES-279 - There is no easy way to get command that will be used for Maven build invocation
- Feature Request
-
- SHRINKRES-281 - Provide FormatProcessor for java.nio.file.Path
- Bug
-
- SHRINKRES-275 - Dowloading/extracting of Maven binaries is not tread-safe
Thanks to the following list of contributors: Matous Jobanek, Hemani, Gunnar Morling