2 reasons
1)it may have been that you triggered a rebuild of the jar and it was interrupted or
2)you pulled an artifact from a repo before the connection completed
Post the build routine for your ear from your pom.xml that you are using
and we can better assist why this particular jar is going 'fubar'
Viel Gluck
M-