Why does Artifactory require an explicit artifact for some Ivy dependencies -


i have artifactory server use resolve ivy dependencies. when want add dependency ivy.xml, have add explicit nested <artifact> tag, , don't understand why.

example a:

<dependency org="com.google" name="guava" rev="[7,)" conf="compile,runtime" /> 

example b

<dependency org="com.twelvemonkeys.common" name="common-image" rev="3.0.1" conf="compile,runtime">   <artifact name="common-image" ext="jar"/> </dependency> 

looking @ cached dependencies in artifactory tree view, there's nothing indicates last example should need info resolve dependency, artifactory suggests itself, , resolution doesn't work without out.

i'm using ivy against repository maven layout. settings generated artifactory , like:

<?xml version="1.0" encoding="utf-8"?> <ivy-settings>   <settings defaultresolver="main" />   <resolvers>     <chain name="main">       <ibiblio          name="public"          m2compatible="true"          root="http://example.org/artifactory/remote-repos" />     </chain>   </resolvers> </ivy-settings> 

why artifactory require explicit artifact ivy dependencies , not others?

edit 20151005: added ivy settings example

the tool performing dependency resolution ivy client , not artifactory. based on dependency deceleration ivy resolver decides artifact request repository (in case artifactory).
artifact feature provides more control on dependency not control ivy file.
enables specify artifacts required, if dependency has no ivy file.
more information artifact feature , when should used consult ivy documentation.


Comments

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -