2.5.0.CR2's version of jee-example-app-1.0.0.ear made it into Maven Central, and now Windup treats it as a known archive and ignores it, resulting in 0 issues when windup is run on the app.

Quick hack fix: we can make a slight modification to the app so the hash doesn't match and Windup stops ignoring it. The same thing can happen to the new version anytime though.

Potential thoughts for fixing:
– Don't treat top-level applications as ignoreable in this way
– Don't treat ears/wars as ignoreable in this way
– Be a little more discriminating in what we ignore than "anything in Maven Central" (how?)