It's not a good idea to rename the jar. The app doesn't care what the jar's name is, and if you remove the version number, you're discarding information that might be important to know someday.
Also, if there's a dependency on a certain version and you force a different version to be included, you may have problems. The reason dependencies carry version identifiers is that they want to make sure apps don't fail because an incompatible version was included.
Most importantly, there's no reason why
you should be including beanutils manually. Beanutils is available as a Maven repository resource, so you should declare it as a dependency if you need to. If it's referenced by one of your other dependencies (such as
Struts), you won't have to, since the dependencies cascade.
If you're customizing BeanUtils for some reason, make the custom BeanUtils a Maven project, use mvn install to install the custom version in your repository and use the dependency mechanism in the same way you would for one of the standard BeanUtils releases.