title: Travis CI not using extra Maven repository provided in pom.xml
body: <p>I have a Java-based GitHub project, <a href="https://github.com/steve-perkins/fitnessjiffy-spring/tree/bootstrap">fitnessjiffy-spring</a> (I'm currently focused on the "bootstrap" branch).  It depends on a library built from another GitHib project, <a href="https://github.com/steve-perkins/fitnessjiffy-etl">fitnessjiff-etl</a>.  I am trying to configure both of these to be built by Travis CI.</p>
  
  <p>Unfortunately, Travis is not as sophisticated as Jenkins or Hudson in dealing with Maven-based Java projects.  Jenkins can easily handle dependencies between projects, but the same concept doesn't seem to exist with Travis.  If one project depends on another, then that other project must already be built previously... and its artifact uploaded to some Maven repo where the first project can download it later.</p>
  
  <p>My "fitnessjiffy-etl" library is building and deploying just fine.  I'm using <a href="https://bintray.com/">Bintray</a> for Maven repository hosting, and you can clearly see my artifacts over plain HTTP at:</p>
  
  <p><a href="http://dl.bintray.com/steve-perkins/maven/">http://dl.bintray.com/steve-perkins/maven/</a></p>
  
  <p>In my "fitnessjiffy-spring" project, I am adding this Maven repo location directly in the <code>pom.xml</code>, so that Travis will be able to find that artifact dependency.  <a href="https://raw.githubusercontent.com/steve-perkins/fitnessjiffy-spring/131dca4ba3130da418e45ae7d047212e2e06b65a/pom.xml">Here is the state of my POM at the time of this writing</a>.  Note the <code>&lt;repositories&gt;</code> element at the bottom of the file.</p>
  
  <p>When I build this project locally, it works just fine.  I can see it downloading the Maven artifact from "<a href="http://dl.bintray.com/">http://dl.bintray.com/</a>...".  However, when I try to build on Travis CI it fails every time.  I can see in the console log that Travis is still trying to download the artifact from Maven Central rather than my specified repo.</p>
  
  <p>Does this make sense to anyone else?  Why does Maven utilize a custom repository location in a POM file when building locally, but ignores this configuration when running on a Travis CI build?</p>