Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow

Created attachment 371203 [details]
root.log

root.log for i386

Created attachment 371204 [details]
build.log

build.log for i386

Created attachment 371205 [details]
mock.log

mock.log for i386

Created attachment 371206 [details]
root.log

root.log for x86_64

Created attachment 371207 [details]
build.log

build.log for x86_64

Created attachment 371208 [details]
mock.log

mock.log for x86_64

Argh, dammit, this seems to be more fallout from the velocity-1.6.3 update in rawhide. The above logs don't show the newest problems, but the current issue can be seen in this attempted scratch build:
    http://koji.fedoraproject.org/koji/taskinfo?taskID=1984580

I'm investigating now, but it seems to be a combination of:
- velocity now contains its own POM
- that POM requires werken-xml, which (until now) didn't have a POM of its own

I've just updated werken-xml to include the necessary maven depmap stuff, but maven2 still doesn't build (as seen above).

The easiest thing would probably be to revert velocity in rawhide, I guess ...

This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Maven will soon be at 2.2.1 in rawhide (http://koji.fedoraproject.org/koji/buildinfo?buildID=180322). It is a completely re-written rpm, and will no longer have this issue. Marking WONTFIX.