Unexpected behavior in uploadArchives after switching to M6

Old Forum
1

Hi there, in one of our java project builds, we add an additional configuration named “releases”. In the artifacts closure we add one zip task to this releases configuration. But after adding the zip task to “releases”, the uploadArchives task also deploys this zip, though I didn’t add it to this archives configuration. For an easier understanding, I’ve added a simple example build script:

apply plugin:'java'
  configurations{
    releases
}
  group = "com.breskeby.test"
version = "0.1-SNAPSHOT"
  task zip(type: Zip) {
    from('content')
 }
  uploadArchives {
    repositories {
       flatDir {
           dirs 'archives'
       }
    }
}
  uploadReleases {
    repositories {
       flatDir {
           dirs 'releases'
       }
    }
}
  artifacts{
    releases zip
}

When running uploadArchives on the sample build script with M5+, I can find the zip and the jar in the archives folder. This was definitely not what I expected to find in “archives” Is this (not well documented) intended behavior or a bug?

regards, René