Project organization suggestions
We working under software which depends on set of external libraries. Two of them developed in-house by our company and they are under heavy development and tuning too. 
So sometimes such list of dependencies create problems, when core application referenced on outdated external libraries. 
As a temporary solution we decided to include into commit of applications binary versions of libraries. But this doesn't looks very nice for me.
I am sure that we not only one company who has such problems:) Which approaches you using?

Our application stack: Java, NetBeans, Subversion, ant 
Project organization suggestions
===

We working under software which depends on set of external libraries. Two of them developed in-house by our company and they are under heavy development and tuning too. 
So sometimes such list of dependencies create problems, when core application referenced on outdated external libraries. 
As a temporary solution we decided to include into commit of applications binary versions of libraries. But this doesn't looks very nice for me.
I am sure that we not only one company who has such problems:) Which approaches you using?

Our application stack: Java, NetBeans, Subversion, ant 