Affects Version/s: 2.2-beta-1
Fix Version/s: 2.2
Environment:java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
When attempting to add a dependency to an assembly without unpacking the dependency using the following snippet of assembly, the dependecies are silently ignored:
It turns out the above config makes no sense - multiple dependencies match the includes rule, and yet an outputFileNameMapping has been defined, which only makes sense when it matches a single include line.
In this case a proper error message needs to be thrown to explain that when outputFileNameMapping is present, only one include can be present. Currently assembly succeeds silently while doing nothing, causing much confusion.