[GRADLE-2745] Setting correct 'type' in dependency does not mask deprecation warning for POM with non-jar packaging Created: 11/Apr/13  Updated: 04/Jun/14  Resolved: 04/Jun/14

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.0-rc-1

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Fixed Votes: 7


In https://github.com/gradle/gradle/blob/master/design-docs/dependency-management-bug-fixes.md#user-visible-changes-1, we stated (in summary):

For dependency with type: 'ext' (anything other than 'jar')
1. If pom.packaging in ['pom', 'jar', 'ejb', 'bundle', 'maven-plugin', 'eclipse-plugin'] will emit a deprecation warning before using 'module.jar'
2. If pom.packaging == 'foo' and 'module.foo' exists, then emit deprecation warning and use module.foo
3. If pom.packaging == 'foo' and 'module.foo' does NOT exist, use 'module.ext'

The problem is the case where pom.packaging == 'ext': In this case we should not be emitting a deprecation warning, I don't think. Otherwise, there's nothing a consumer can do to avoid the deprecation warning and consume a 'war' artifact from a module with pom.packaging == 'war'.

Generated at Wed Jun 30 12:30:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.