Synchonize OODT-CAS components, which depend on one another, on a particular Apache-Tika version

cas-metadata and cas-pushpull depend on 2 different versions of Apache Tika:

cas-metadata:

[INFO] [dependency:tree]
[INFO] org.apache.oodt:cas-metadata:jar:0.2-incubating
...
[INFO] +- org.apache.tika:tika:jar:0.3:compile
...

cas-pushpull:

[INFO] [dependency:tree]
[INFO] org.apache.oodt:cas-pushpull:jar:0.2-incubating
...
[INFO] +- org.apache.oodt:cas-metadata:jar:0.2-incubating:compile
[INFO] |  +- org.apache.oodt:pcs-input:jar:0.2-incubating:compile
[INFO] |  +- org.apache.tika:tika:jar:0.3:compile
...
[INFO] +- org.apache.tika:tika-core:jar:0.8:compile
...

When mvn package is run, the lib directory is populated with both: tika-0.3.jar and tika-core-0.8.jar

• so what is happening is pushpull is really using tika-0.3.jar instead of tika-core-0.8.jar, since java classloader loads the first class it finds for the given classpath from the first jar it finds which is tika-0.3.jar since it ascii sorts before tika-core-0.8.jar