[GRADLE-1473] Maven and Application plugins conflict on the "install" task Created: 13/Apr/11  Updated: 04/Jan/13  Resolved: 22/Apr/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-2
Fix Version/s: 1.0-milestone-3

Type: Bug
Reporter: Brian Trezise Assignee: Peter Niederwieser
Resolution: Fixed Votes: 0


If you try to apply the maven plugin and the application plugin to the same project, you get an error stating that a task with the name "install" already exists.

See here:


and here:


Comment by Peter Niederwieser [ 22/Apr/11 ]

For the time being we should probably just rename one of the tasks (suggestions?), but in the longer term I think we need something better (e.g. qualified and unqualified task names).

Comment by René Gröschke (Inactive) [ 22/Apr/11 ]

maybe installApplication? I think what the maven install task does is not a "installation" it's more a deploy or staging in my opinion. But the corresponding maven goal is also called 'install' isn't it?


Comment by Peter Niederwieser [ 22/Apr/11 ]

I've renamed the install task of the application plugin to 'installApp'.

Generated at Wed Jun 30 11:56:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.