title: Reusing maven configuration
body: <p>What is the best way to create reusable dependency definitions and profiles in maven?</p>
  
  <p>I would like to externalize dependencies and profiles for integration tests to a separate pom, which can be included in other maven projects (not inheriting from a single parent pom). Later i can activate the profiles when running integration tests on different application servers both from console and eclipse.</p>
  
  <pre><code>integrations-tests
      pom.xml (contains Arquillian dependencies and profiles)
          profile:jboss-remote
          profile:tomcat-embedded
          dependencies:Arquillian,Java EE,MavenShrinkWrap etc.
  project1
      pom.xml
          dependency:integration-tests (or other way to include)
  project2
      module1
          pom.xml
              dependency:integration-tests (or other way to include)
  
  mvn test -P jboss-remote (profile from integrations-tests)
  mvn test -P tomcat-embedded (profile from integrations-tests)
  </code></pre>
  
  <p>I don't want to mess with local settings.xml, since the profiles should be reusable by many developers and CI servers.</p>