Answers: <p>I'd go with (2). Since Bob has a more rigid setup (requires Maven metadata), and Alice can provide that (using more flexible Ant), that sounds like the easiest way to go.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-01-04T00:01:34.510Z
Answers: 2019-01-04T00:01:34.510Z
Answers: JBaruch
Body: <p>Consider the following situation:</p>
  
  <pre><code>Alice -----              { Firewall }  Bob
  |                                       |
  Artifactory / Ivy repos  -  ---   --- Nexus / Maven Repos
  </code></pre>
  
  <p>That is, Alice uses Ant and Ivy to publish her artefacts in an Artifactory in Ivy repos, while Bob sits behind a firewall and builds Maven artefacts storing them in Maven repos in Nexus.</p>
  
  <p>How can Alice provide her artefacts to Bob? (while both do not have to make large changes to their setup)</p>
  
  <p>So far, I have considered the following options and decided to ask you before trying them out:</p>
  
  <p>(1) Bob manages credentials to access Alice' artefacts in his build system and uses a <a href="https://axonivy.github.io/project-build-plugin/release/7.1/index.html" rel="nofollow noreferrer">Maven plugin for Ivy</a> (which means configuration work for all relevant projects)</p>
  
  <p>(2) Alice uses <a href="http://ant.apache.org/ivy/history/latest-milestone/use/makepom.html" rel="nofollow noreferrer">an Ant/Maven <em>task</em></a> to generate POMs for <em>publishing/deployment</em> step and offers an additional Maven repo, because Artifactory can support it different repo formats. This for Bob's most convenience though Alice needs to do configuration work of all relevant projects and there might be also other Bobs in future using other <em>binary repository managers</em>.</p>
  
  <p>(3) Bob configures Nexus to be a proxy for Alice' Ivy repo (which is AFAIK was <a href="https://stackoverflow.com/questions/25910800/does-nexus-oss-support-proxying-of-ivy-repos">not possible</a> as of 2014).</p>
  
  <p>What would you do?</p>
  
Tags: <maven><artifactory><ant>
Title: How to use remote Ivy artefacts in Maven jobs with different binary repository managers?
UserDisplayName: Ta Mu
ThreadText: # How to use remote Ivy artefacts in Maven jobs with different binary repository managers?
  
  (Asked by: username_0 on 2018-09-11)
  
  Consider the following situation:
  
  ```
  Alice -----              { Firewall }  Bob
  |                                       |
  Artifactory / Ivy repos  -  ---   --- Nexus / Maven Repos
  
  ```
  
  That is, Alice uses Ant and Ivy to publish her artefacts in an Artifactory in Ivy repos, while Bob sits behind a firewall and builds Maven artefacts storing them in Maven repos in Nexus.
  
  How can Alice provide her artefacts to Bob? (while both do not have to make large changes to their setup)
  
  So far, I have considered the following options and decided to ask you before trying them out:
  
  (1) Bob manages credentials to access Alice' artefacts in his build system and uses a [Maven plugin for Ivy](https://axonivy.github.io/project-build-plugin/release/7.1/index.html) (which means configuration work for all relevant projects)
  
  (2) Alice uses [an Ant/Maven *task*](http://ant.apache.org/ivy/history/latest-milestone/use/makepom.html) to generate POMs for *publishing/deployment* step and offers an additional Maven repo, because Artifactory can support it different repo formats. This for Bob's most convenience though Alice needs to do configuration work of all relevant projects and there might be also other Bobs in future using other *binary repository managers*.
  
  (3) Bob configures Nexus to be a proxy for Alice' Ivy repo (which is AFAIK was [not possible](https://stackoverflow.com/questions/25910800/does-nexus-oss-support-proxying-of-ivy-repos) as of 2014).
  
  What would you do?
  
  **Tags:** maven, artifactory, ant
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-01-04. Score: 1
  
  I'd go with (2). Since Bob has a more rigid setup (requires Maven metadata), and Alice can provide that (using more flexible Ant), that sounds like the easiest way to go.
  
  
  ---
  
  