Subproject depends on configuration from other subproject, but subproject build order doesn't respect that

The other conversation is on How to depend on WAR file built by project, not the jar file? , but Mark V is still replying on that thread with my essential change of subject, so perhaps I’ll get it resolved there.

However, that thread doesn’t really talk about the structure of the two WAR build files, as they’re pretty simple, but both of them now have the following so I can depend on the “war” configuration from another project:
`configurations {
war {}
}

artifacts {
war tasks.war
}`