[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] Can I request a new release of libvirt-java?

On 09/16/2013 07:58 AM, Daniel Veillard wrote:
   Raising this due to maven

On Fri, Sep 13, 2013 at 05:26:24PM +0800, Daniel Veillard wrote:
On Fri, Sep 13, 2013 at 11:13:53AM +0200, Wido den Hollander wrote:


   Indeed that was the problem, I just commited the fix, thanks !

   Hum, getting back on-list, I pushed everything including maven
files at their location, unfortunately this never shows up in repos

  Seems that to be indexed one need to push to an expernal repo
within that small list:

I had this discussion last year as well with somebody else from RedHat and we ended up the the conclusion that libvirt-java wouldn't go to Maven Central.

In the CloudStack project we simply added libvirt.org as a extra repository: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=plugins/hypervisors/kvm/pom.xml;h=4c0ec982bdf1ebc6c2fc3d649759f6cfe5be88d1;hb=master#l22

I also just tried libvirt-java 0.5.0, it works for what we are using :)


"Instead of maintaining repository rsync feeds for each projects, we now
encourage projects to use an approved repository hosting location.

Currently approved repository hosting locations:

     Apache Software Foundation (for all Apache projects)
     Codehaus (for Codehaus projects)
     FuseSource Forge (focused on FUSE related projects)

  We are definitely not Apache Software Foundation, nor Codehaus, nor
FuseSource, and I have no idea what Nuiton.org might be nor intent to
push to a random place.



Having each project maintain its own repository with rsync to Central
Repository used to be the preferred process until January 2010. But we
are no longer accepting rsync requests on a per project basis.

Over time, we have learned that this process is not scalable. Many of
the projects being synced release very infrequently, yet we have to hit
hundreds of servers several times a day looking for artifacts that don't
change. Additionally, there is no good mechanism currently for
validating the incoming data via the rsync, and this leads to bad
metadata that affects everyone.

The aggregation of projects into single larger feeds allows us to sync
faster and more often, and ensuring these locations perform sufficient
checks increases the quality of metadata for everyone."

   As a result current repos only list libvirt-java up to 0.4.7 and none
of the newer versions.

   Repository are evil, and they built a solution based on those.
The bug is on their side, I won't upload to $random_site, so unless
someone else pulls from libvirt.org, libvirt-java maven won't index
more recent build.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]