[GRADLE-1642] Maven plugin assumes the base plugin has been applied Created: 24/Jun/11  Updated: 04/Jan/13  Resolved: 24/Jun/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-milestone-4

Type: Bug
Reporter: Luke Daley Assignee: Luke Daley
Resolution: Fixed Votes: 0


Among other things, the maven plugin references the "archives" configuration so is making assumptions about functionality that is added by the base plugin.

This is usually ok because almost always the maven plugin is being used in conjunction with the Java or Groovy plugins, but this doesn't have to be the case. Given that plugin application is idempotent, the maven plugin should apply the base.

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