How do I expose a class from one WAR being referenced by TLD file in another in WebSphere

When I run WebSphere locally, I am getting "Failed to open resource" warnings because an entry in my app.tld file is referencing a base class in another WAR in the same EAR.

I don't have control over deployment, so jar'ing up these class files isn't a good solution for me. The only other feasible solution I can come up with is creating a subclass in my WAR, but due to our source control, I would have to check out all the subclasses manually when the base class changes.

I tried playing with classloader settings with no luck as well. Any suggestions/best practices on how to handle this situation?