Hi,
the problem is that both plugins (maven and application) do declare a
install task. this issue was dicussed on that mailinglist before. have a
look at
http://gradle.1045684.n5.nabble.com/The-maven-and-application-plugins-td4262169.html
where adam provided a workaround. I think there wasn't a jira raised
yet. could you do that? regards,
René
Am 13.04.11 23:46, schrieb StormeHawke:
I should clarify, this IS a conflict with the maven plugin, just commented it
out as a test. Has anybody run into this? Any workarounds?
--
View this message in context:
http://gradle.1045684.n5.nabble.com/gradle-application-plugin-task-with-name-install-already-exists-tp4301699p4301702.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
-----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email