Bug fix in the 'lib' target.

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.
This commit is contained in:
Jonathan Bernard
2011-11-29 16:40:55 -06:00
parent d78bd3386e
commit 8e77c4045c
2 changed files with 5 additions and 3 deletions

View File

@ -0,0 +1,13 @@
<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>