8e77c4045c
The 'lib' target was inteded to be a target the project-specific build could override. However, the common build was using it to create dependancies on '-lib-local' and '-lib-ivy'. If a project-specific build ovverrode lib and forgot to add those dependancies it would break. The project-specific builds should not be required to know about the internal dependancies of the common build. A new target '-lib' was created, which depends on '-lib-local', 'lic-ivy', and 'lib'. 'lib' is not an empty target that is safe to be overridden.
14 lines
726 B
XML
14 lines
726 B
XML
<ivysettings>
|
|
<settings defaultResolver="default">
|
|
<resolvers>
|
|
<sftp name="public" user="ivy" keyFile="resources/ivy/id_jdblabs_ivy" host="jdb-labs.com">
|
|
<ivy pattern="/home/ivy/repository/[organisation]/[module]/ivys/ivy-[revision].xml"/>
|
|
<artifact pattern="/home/ivy/repository/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>
|
|
</sftp>
|
|
</resolvers>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-shared.xml"/>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-local.xml"/>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-main-chain.xml"/>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-default-chain.xml"/>
|
|
</ivysettings>
|