Which sounds like a "uses" relationship which, AFAIK, should not be a problem at deployment time because [b]when being deployed[/b] B should not be trying to access A. If it is, [b]I[/b] would remove that access because it is inherently fragile.
If the dependency is actually on class definitions (that is, the jars for the interfaces that B uses) then you should deploy the used interfaces with B in its jar file. Yes, this means some duplication but it is in fact correct because the interfaces are what B needs and A is just one possible source of the implementation.
[Message sent by forum member 'matterbury' (matterbury)]
http://forums.java.net/jive/thread.jspa?messageID=356743