I’m trying to migrate our existing Gradle build which initially used Gradle 1.0-m3 to Gradle 1.0-m5, but I noticed something unusual in the handling of published artifacts - it seems that now every published artifact is also added to the archives configuration.
Our build was configured to expect only production artifacts in the archives configuration, while we also added separate ‘sources’, ‘docs’ and ‘tests’ configurations to hold the source, javadoc and integration test archives respectively. With Gradle 1.0-m5 those artifacts also appear in the archives configuration and are delivered as part of the product.
What is the reason for this behavior and is there a way to switch it off? Does this mean that to migrate to 1.0-m5 we need to have a separate configuration in addition to the archives configuration, which would serve as a container for production binaries instead?