Michael Bayne
e648cfc7bd
Why does the Java dependency management world have to suck so badly? Is it not
crazy to want projects to be able to publish their own releases and to make it
easy for other projects to depend on those published releases? Why do I have to
reconfigure the standard configuration to add new repository sources? Why
doesn't the IvyRep resolver work and do something sophisticated?
Why can't I just fucking put in my ivy.xml:
<dependency org="com.samskivert" name="samskivert" rev="1.0" conf="runtime"
source="http://samskivert.googlecode.com/svn/releases"/>
and have Ivy do something smart like assume that there will be a standard
directory structure at the specified root and that it will contain the ivy.xml
and module.jar file that it needs, and just download them?
Instead I have to write a ton of fucking boilerplate and wire it all in via a
separate ivysettings.xml file, and then helpfully instruct anyone who uses my
fucking library that they too can have the pleasure of doing the same.
16 lines
649 B
XML
16 lines
649 B
XML
<ivysettings>
|
|
<settings defaultResolver="default"/>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-local.xml"/>
|
|
<include url="${ivy.default.settings.dir}/ivysettings-public.xml"/>
|
|
<resolvers>
|
|
<chain name="default" returnFirst="true">
|
|
<resolver ref="local"/>
|
|
<resolver ref="public"/>
|
|
<url name="samskivert">
|
|
<ivy pattern="http://samskivert.googlecode.com/svn/releases/[organization]/[module]/[revision]/[artifact].xml"/>
|
|
<artifact pattern="http://samskivert.googlecode.com/svn/releases/[organization]/[module]/[revision]/[artifact].[ext]"/>
|
|
</url>
|
|
</chain>
|
|
</resolvers>
|
|
</ivysettings>
|