using archiva as ivy repository

[Brown, Carlton-2]

I am looking at the feasibility of using Archiva as an ivy repository
and I'm not finding much.   Does anyone have any suggestions, notes, or
best practices for doing this?

 

For a moment I thought I found a good doc at
http://maven.apache.org/archiva/userguide/using-ivy.html which has the
promising title of "Using Repository as an Apache Ivy Repository".
Unfortunately, the published content contains only the line ":STUB: This
is a documentation stub."   Could I induce anyone to share a draft copy
of that document?

 

TIA,

Carlton




-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission.  Thank you.
====================================================

[Alan Plante]

I've started looking at this too.  Archiva has a real nice mgmt ui over a repository so I'd like to be able to use that on top of my Ivy repository.

Unfortunately I came across the same link as you did but haven't found anything more than that.

-Al

Brown, Carlton-2 wrote:

I am looking at the feasibility of using Archiva as an ivy repository
and I'm not finding much.   Does anyone have any suggestions, notes, or
best practices for doing this?

For a moment I thought I found a good doc at
http://maven.apache.org/archiva/userguide/using-ivy.html which has the
promising title of "Using Repository as an Apache Ivy Repository".
Unfortunately, the published content contains only the line ":STUB: This
is a documentation stub."   Could I induce anyone to share a draft copy
of that document?

[rarabaolaza]

Hi,

I´m using ivy with archiva (with http authentication) probably i´m not doing it the best way but it works.
 
In my ivysettings.xml file i use a ibiblio resolver:

<ivysettings>
  <settings defaultResolver="archiva" />
  <resolvers>
    <ibiblio name="archiva" m2compatible="true" root="[repositoryPath]"/>
  </resolvers>
</ivysettings>

And in my build xml i use the ivy:settings tag to configure authentication

<target name="resolve" description="--> retreive dependencies with ivy">

    <ivy:settings file="./ivysettings.xml">
                        <credentials host="192.168.215.43"  realm="Repository [YourRepositoryName]" username="user" passwd="passwd" />
                </ivy:settings>
        <ivy:retrieve />
    </target>

Don´t forget to replace repositoryPath and YourRepositoryName with  your archiva repository path and name. (You can see it on archiva repositories screen)

It works fine for me :)

Best Regards, Raúl    

-----Mensaje original-----
De: Alan Plante [mailto:applante@...]
Enviado el: lun 21/07/2008 20:23
Para: users@...
Asunto: Re: using archiva as ivy repository
 

I've started looking at this too.  Archiva has a real nice mgmt ui over a
repository so I'd like to be able to use that on top of my Ivy repository.

Unfortunately I came across the same link as you did but haven't found
anything more than that.

-Al


Brown, Carlton-2 wrote:

>
> I am looking at the feasibility of using Archiva as an ivy repository
> and I'm not finding much.   Does anyone have any suggestions, notes, or
> best practices for doing this?
>
> For a moment I thought I found a good doc at
> http://maven.apache.org/archiva/userguide/using-ivy.html which has the
> promising title of "Using Repository as an Apache Ivy Repository".
> Unfortunately, the published content contains only the line ":STUB: This
> is a documentation stub."   Could I induce anyone to share a draft copy
> of that document?
>

--
View this message in context: http://www.nabble.com/using-archiva-as-ivy-repository-tp15161852p18574568.html
Sent from the archiva-users mailing list archive at Nabble.com.



------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion
confidencial destinada solamente a la(s) persona(s) mencionadas
anteriormente. Pueden estar protegidos por secreto profesional Si usted
recibe este correo electronico por error, gracias de informar inmediatamente
al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
Origin no se hace responsable por su contenido. Su contenido no constituye
ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por
ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus
------------------------------------------------------------------

[Gregory Boissinot]

Archiva is a Maven repository manager. It’s Maven centric.
So, you need to deploy Maven artifacts and you have to generate a Maven descriptor (pom.xml).

How are you doing that?
It seems it’s not possible with only the Ivy tool.

In my opinion, you have to use alternatively Maven Ant Tasks or the new build system Gradle that provides this feature.

Any feedback would be appreciated.

Thanks very much
--
Gregory

[Gregory Boissinot ()]

I found the solution by using the Ant Ivy task <ivy:makepom/> (
http://ant.apache.org/ivy/history/latest-milestone/use/makepom.html).

This task generates a Maven 2 pom.xml, I can publish (with <ivy:publish/>) the target artifact and the pom.xml into Archiva.
And it's OK.