Can ivy install and retrieve configurations from Maven repository? -



Can ivy install and retrieve configurations from Maven repository? -

i have local filesystem ivy repository , need install (publish) artifacts remote maven repository nexus or artifactory. wrote ant script ivy install task along next lines:

class="lang-xml prettyprint-override"><ivy:install organisation="apache" module="commons-lang" revision="2.0" from="ivyfilesys" to="remotemaven"/>

now, there multiple configurations in local ivy repository (test, compile), these declared in ivy.xml files nowadays there. local repository consists of 2 folders per artifact, jars , ivys. jars folder contains jars , ivys folder contains ivy.xml configurations declared inside. sha , md5 checksum files nowadays nil else.

i expected ivy tell maven repository available configurations seems not. after switch newly created repository resolution, ivy cannot find artifacts has installed there itself, claiming test , compile configurations missing.

local repository configured file-based , artifacts can resolved there no problem. remote repository ibiblio, m2compatible:

class="lang-xml prettyprint-override"><ibiblio name="remotemaven" m2compatible="true" root="http://my.server:8081/" pattern="[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/> />

root configured our server. root , authentication configured correctly installed artifacts appear on server.

is way create ivy respect own ivy.xml , install nexus or artifactory repository configurations, later resolve them?

maybe ivy:install task needs more options? maybe configuration files missing or incomplete?

can ivy install , retrieve configurations maven repository?

the simple reply no.

how ivy interprets maven repo

maven not back upwards ivy's concept of configurations. closest comparing maven "scopes". these fixed , ivy's ibiblio resolver understands how map these configuration. next reply has more detailed description:

how maven scopes mapped ivy configurations ivy how ivy pushes file maven repo

when publishing artefact maven repository must generate maven metadata file: pom.xml. makepom task allows specify ivy configurations should used particular maven scope. next answers might prove useful:

convert ivy.xml pom.xml how publish 3rdparty artifacts ivy , nexus publishing multiple artifacts maven repository using ivy ivy makepom marks dependencies optional despite mapping

ivy not restricted fixed number of scopes. while ivy configurations much more flexible, cannot assume each configuration beingness utilize populate standard project classpaths....

bulk loading maven repo

so in conclusion mass transfer files local ivy repo maven repository not trivial exercise next reasons:

translating ivy files maven poms can hard. ivy's configurations not work same maven scopes. your local repository might contain files in maven central , don't need explicitly uploaded.

in experience biggest problem big numbers of 3rd party jars no record of came from. assist in maven-izing new projects developed groovy script uses nexus search api find matching records in maven central database. speaking approach results in reduction in number of jars locally stored much 80%.

https://github.com/myspotontheweb/ant2ivy

hope helps.

maven repository ivy buildconfiguration

Comments

Popular posts from this blog

xslt - DocBook 5 to PDF transform failing with error: "fo:flow" is missing child elements. Required content model: marker* -

mediawiki - How do I insert tables inside infoboxes on Wikia pages? -

Local Service User Logged into Windows -