archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felipe Roos da Rosa <>
Subject Enc: Archiva OMG RAS extension
Date Fri, 10 Oct 2008 18:57:52 GMT
Hi James & Brett!

It's being a while since the last email, but only now I had the chance to perform some investigation.
Now that I did, some other question came up.

I took an overall look at the archiva running it on my machine. I've also downloaded the
svn repository for writing a plugin, but I could not get that sample working yet (i'm working
on - with some luck, i've an environment problem). I would like to ask you some things about
the repository, and how can I handle the generation of pom files.

As long as I understood, we can write a repository content consumer so archiva tells us when
a new artifact is added to the repository. In our context, we would process a ".ras" file,
and generate the "pom.xml" that makes referente to it. Is that correct? Where can I find
more resources about the process archiva uses to call its consumers?

Another thing is that when browsing through archiva for an artifact, I believe that the
information archiva shows about the artifact comes from the pom.xml file. If so, is there
any way to change layout/content of the artifact page so we can show customized information
about the artifact? 

Last, but not least, a RAS repository must be enabled with two URLs that support POST actions
(stated in the spec). One performs searches by keyword, and return a list of assets. The
other performs a search by logical path and brings back a single asset. Is there a way to
build that inside archiva? Otherwise I would have to write a HTTP wrapper that peform searches
to archiva...

Thanks for all your support. 
Kind regards, 
Felipe Roos 

Achar desculpas para os nossos 
defeitos não nos torna melhores 

----- Mensagem encaminhada ----
De: "Roos, Felipe (R&D Brazil)" <>
Para: "" <>
Enviadas: Sexta-feira, 10 de Outubro de 2008 15:28:20
Assunto: FW: Archiva OMG RAS extension

Felipe Roos
HP R&D Brazil
55 51 21213560
From:Joana M. F. Trindade [] 
Sent: domingo, 7 de setembro de 2008 03:14
Cc: Roos, Felipe (R&D Brazil)
Subject: Re: Archiva OMG RAS extension
Hi Brett,

Thanks for the support, that would be really great :-)

At first, we considered implementing our own format of repository. Since OMG does not define
a specific format or metadata for RAS repositories per se, however, we thought that going
for a Maven repository with RAS artifacts would require considerably less effort. Maven already
has dependency management, and concerning repository managers it seems that Archiva offers
most of the tasks we were going to implement ourselves from scratch. By reusing Maven, we
can focus on implementing support for processing RAS artifacts metadata as defined in the

I understand this is preliminary documentation, but we would really appreciate if you can
provide pointers for samples (e.g., are there any specific roles, role-hint values in the
plexus component definition we should be aware of?) so we can write our own consumer.

On Sat, Sep 6, 2008 at 12:05 AM, Brett Porter <> wrote:

I'd be very happy to help you with this and improve our documentation / extension mechanism
in the process.

What are you looking to achieve with it? Is it a different format of repository, or a Maven
repository containing RAS artifacts and wanting to process them in some special way?

The latter is partially supported by writing your own consumer. The preliminary documentation
we have for that is here:

(BTW, I'm removing the users@ CC to avoid confusion.)


On 06/09/2008, at 7:54 AM, Joana M. F. Trindade wrote:

A colleague and I would like to extend Archiva to support repositories for
artifacts, as defined in the OMG Reusable Assets Specification [1]. Is there
development guide for Archiva extensions?


Joana M. F. da Trindade

Personal Homepage:
Brett Porter

Joana M. F. da Trindade

Personal Homepage:

      Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message