[GRADLE-282] Inconsistent API for WAR resp. archive tasks Created: 24/Oct/08 Updated: 04/Jan/13 Resolved: 24/Nov/10 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.4 |
| Fix Version/s: | 0.9-rc-1 |
| Type: | Bug | ||
| Reporter: | Martin Vlcek | Assignee: | Tom Eyckmans |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
The naming and behavior of the archive task methods is confusing:
When used with the libs { war(...) }of the WarPlugin for a second war file (e.g. mockup of a web service) this means that
Suggestions:
|
| Comments |
| Comment by Hans Dockter [ 15/Apr/09 ] |
|
Tom plans to rewrite the war task for 0.7 (and implement an ear task). |
| Comment by Adam Murdoch [ 24/Mar/10 ] |
|
Can we close this, given we have reworked the archive task APIs, and the war task is now consistent with the other archive tasks? |