Affects Version/s: 2.2
Fix Version/s: None
mvn 2.2.1, mvn 2.0.9, mvn 2.1.0
Number of attachments :
The classic use case is when you use multi-module project.
pomA (packaging pom)
-> pomB (packaging jar)
-> pomC (packaging jar)
-> pomD (packaging pom)
pomB,C,D inherit from pomA
We define common plugin configuration into pomA, for example say to jar plugin to build test jar.
but in some case it make not sense (for example when pom is type of 'pom') and in this case an empty jar is construct (then uploaded when we deploy)
Maybe a check to detect zip file is empty could be sufficient or attache this plugin only on specific pom packaging (jar/war/ear ...)
I have attached a sample, just unzip and run mvn package inside "test" directory.