mirror of https://github.com/sbt/sbt.git
More about mvn vs. ivy proxies
This commit is contained in:
parent
44650ca89f
commit
88ca4aec64
|
|
@ -29,7 +29,8 @@ the big three being (in alphabetical order):
|
||||||
* Nexus_
|
* Nexus_
|
||||||
|
|
||||||
Once you have a proxy repository installed and configured,
|
Once you have a proxy repository installed and configured,
|
||||||
then it's time to configure SBT for your needs.
|
then it's time to configure SBT for your needs. Read the
|
||||||
|
note at the bottom about proxy issues with ivy repositories.
|
||||||
|
|
||||||
|
|
||||||
sbt Configuration
|
sbt Configuration
|
||||||
|
|
@ -109,6 +110,23 @@ repository file.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Proxying Ivy Repositories
|
||||||
|
=========================
|
||||||
|
The most common mistake made when setting up a proxy repository for
|
||||||
|
sbt is the attempting to *merge* both *maven* and *ivy* repositories
|
||||||
|
into the *same* proxy repository. While some repository managers will
|
||||||
|
allow this, it's not recommended to do so.
|
||||||
|
|
||||||
|
Even if your company does not use ivy, sbt uses a custom layout to
|
||||||
|
handle binary compatibility constraints of its own plugins. To ensure
|
||||||
|
that these are resolved correctly, simple set up two virtual/proxy
|
||||||
|
repositories, one for maven and one for ivy.
|
||||||
|
|
||||||
|
Here's an example setup:
|
||||||
|
|
||||||
|
.. image:: proxy-ivy-mvn-setup.png
|
||||||
|
|
||||||
|
|
||||||
.. _Archiva: http://archiva.apache.org/
|
.. _Archiva: http://archiva.apache.org/
|
||||||
.. _Artifactory: http://www.jfrog.com/home/v_artifactory_opensource_overview
|
.. _Artifactory: http://www.jfrog.com/home/v_artifactory_opensource_overview
|
||||||
.. _Nexus: http://www.sonatype.org/nexus/
|
.. _Nexus: http://www.sonatype.org/nexus/
|
||||||
|
|
|
||||||
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Loading…
Reference in New Issue