By the way,
in preparation for the OBR support in Archiva, at Karaf, I created Karaf
Cave which provides OBR support (as a kind of PoC for Archiva OBR support):
http://karaf.apache.org/manual/cave/latest/user-guide/index.html
What I do is to proxy an Archiva repository with Cave: Cave adds the OBR
repository metadata on front of the Archiva repository.
For instance:
karaf@root()> cave:repository-create obr-proxy
karaf@root()> cave:repository-proxy obr-proxy
http://host:8082/archiva/repository
Regards
JB
On 07/23/2014 09:04 AM, Jean-Baptiste Onofré wrote:
Hi Matt,
I started to implement OBR support in Archiva but I had to switch to
other projects.
I can push my changes on a branch and I will rework on it.
More than OBR (which is likely end of life), I will add Karaf features
native support and OSG subsystem support too.
Regards
JB
On 07/23/2014 08:57 AM, Olivier Lamy wrote:
On 21 July 2014 09:08, Matt Magoffin <[email protected]> wrote:
Cool - in that case you should be able to implement RepositoryListener:
https://github.com/apache/archiva/blob/master/archiva-modules/metadata/metadata-repository-api/src/main/java/org/apache/archiva/repository/events/RepositoryListener.java
That's hooked into most deletion events within Archiva.
That's interesting, thank you. I will look into this API.
Is there a way to know, however, if the user has initiated a full
directory scan from the UI, so that I might recreate the metadata.xml
from
scratch? I thought this would be nice, just in case something is missed
you have the boolean executeOnEntireRepo
I reckon the api could be improve to be more easily extensible but
this need to fully break the api....
That's great. I'm not an OBR user but there are others here that
are. IS
this something you're interested in seeing shipped with Archiva by
default?
Yup sounds really interesting.
I of course have a need for this OBR support, and would think it
wonderful
if Archiva shipped with support by default, yes! The OBR metadata
file can
get rather large, so I had thought long term I'd need to add support for
only including the latest versions of all artifacts in the published
file.
I did license my code as GPLv2, but would be happy to switch that to an
Apache license if that would be helpful.
@apache we cannot accept any GPLv* contributions.
So yes if you want to contribute it, you must change it to Apache
license.
Olivier
-- m@
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
