I believe this is to make absolutely certain that there is no confusion about which file should receive the modified bytes
Ok, thanks. This check is also present in the JBossRetro weaver, so I'm trying to understand why we need it there.
Adrian, could we remove this check from jbossretro? It seems that the src element of the jbossretro task is sufficient for identifying which class is being woven?
The check looks irrelevant for JBossRetro.
You already know what you want to modify.
It might be worthwhile leaving it as a warning (when verbose is enabled)
in case it does cause unexpected problems.