Major Description
I have the issue done to the order of the buildfile instructions. E.g. this order:
define 'testwar' do
project.version = 1.0
package(:war)
project.resources.from(_('src/main/java')).exclude('*.java')
end
With no existing src/main/resources directory means project.resources is nil when package(:war) is called.
If the custom resources call (project.resources.from...) is put before the package(:war) command, then resources is no longer nill, and they end up in the war's classes directory just fine.
This is a boundary case bordering on user error--not having a src/main/resources, and defining my own resources after calling package, but I was under the impression the declarative nature of the package/project.resources lines insinuated order was not important.
Given I can just reorder the lines, this isn't a big deal, but still filling the bug in case there is a way to make it more user-error proof.