On 08/15/2013 11:00 AM, Wido den Hollander wrote: Can I give this one a small bump? Wido

On Mon, Sep 02, 2013 at 08:14:33AM +0800, Daniel Veillard wrote: Hi Wido, I tried to do this today, but I hit a problem, when I run ./autobuild.sh on fedora-19 it starts to build goes fine, was failing in rpm due to broken (fixed in git now), but for some reason it does not produce target/libvirt-0.5.0.jar (after fixing the build version to be 0.5.0) it does build target/libvirt-java-0.5.0.tar.gz target/libvirt-0.5.0-javadoc.jar and target/libvirt-0.5.0-sources.jar but not the binary jar. But it does seems to compile correctly: ------------- .... [javac] Compiling 64 source files to /home/veillard/rpms/BUILD/libvirt-java-0.5.0/target/classes init: [copy] Copying 1 file to /home/veillard/rpms/BUILD/libvirt-java-0.5.0 build: docs: [mkdir] Created dir: /home/veillard/rpms/BUILD/libvirt-java-0.5.0/target/javadoc [javadoc] Generating Javadoc ... BUILD SUCCESSFUL Total time: 5 seconds + exit 0 .... --------------- I'm puzzled, how can the build be successful if the main jar is not generated ??? Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

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 ! Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

Raising this due to maven On Fri, Sep 13, 2013 at 05:26:24PM +0800, Daniel Veillard wrote: [...] 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: "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) Nuiton.org " 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. http://maven.apache.org/guides/mini/guide-central-repository-upload.html " Explanations 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. Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

On 09/16/2013 07:58 AM, Daniel Veillard wrote: Somewhat related to this: It seems you have compiled with Java 7 causing the bindings not to work with Java 6. A lot of users are still running Java 6 on their systems. You could do this with in build.xml: <javac target="1.6" .../> Or something like: <property name="javac.target" value="1.6" /> .. <javac target="${javac.target}" .../> Java 6 is still around and I think it should be supported for older platforms. Wido

On 09/17/2013 09:23 AM, Daniel Veillard wrote: Sure, but if the code in libvirt.org/maven2 is Java 1.7 systems building with Maven and using Java 1.6 can't use it. There is no special code in libvirt-java which requires Java 1.7 to operate. By setting the source and target version to 1.6 the code will run on at least 1.6, but will work just fine on 1.7 systems. It's mainly a compatibility thing. Just sent a patch :) Wido

On 09/17/2013 11:13 AM, Daniel Veillard wrote: No problem! But the current situation is that the 0.5.0 version out there only works with Java 7. Maybe release a 0.5.1 which is compiled for Java 1.6? I don't have push permissions on the libvirt-java repo. Wido