[GRADLE-425] weird behaviour of archive task with multiple projects Created: 23/Mar/09  Updated: 04/Jan/13  Resolved: 15/Apr/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.5.2
Fix Version/s: 0.6

Type: Bug
Reporter: Erwan Lacoste Assignee: Hans Dockter
Resolution: Fixed Votes: 0


In a multiple project environment, java and web plugins used.
Running the gradle archive_war -Dskip.test=true command will result in generating a WAR file NOT including the depending jar from required sub-projects in the archive file.

In case of deploying to a repository, it would be wise to either disable test skipping, by either launching an error, or a warning to point out that no deploy can be done without complete testing.

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