Hi Cristopher, sorry for delay, but I was on vacation. On 11/16/2015 05:26 PM, Christopher wrote: > What's the best way to deal with resolving ivy dependencies in EPEL7? I'm > trying to package zookeeper for EPEL7, and am running into problems. > > I see there's ivy-local for F21 and later, which comes with xmvn 2, but it > looks like EL7/EPEL7 is mostly a F19-era package set. > > Are there any plans to bump xmvn to 2 for EPEL7, or to provide ivy-local > another way? Or is there another option? I'm really more familiar with > maven builds than ivy, so this is somewhat of a struggle. > > Any advice would be appreciated. XMvn/Ivy integration (ivy-local et al.) was added quite recently and it's not supported in RHEL7/EPEL7. Probably the easiest solution is not using Ivy to resolve build dependencies. You would need to use build-jar-repository to create "lib/" directory with all necessary dependencies and patch build.xml not to use Ivy, but JAR symlinks from "lib/". Let me know if you have any trouble with doing that and I'll try to help. Another (probably better long-term) solution would be packaging latest XMvn/javapackages for EPEL7. This could help porting other packages from current Fedora to EPEL7, if not now then in future. Unfortunately I don't have time to do that myself, but anyone is free to do that. -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
