Quoting Michel Alexandre Salim (2012-06-08 15:55:29) > Part of the rationale is that Kushal Das (cc:ed) and myself would like > to eventually write some Fedora infrastructure in Clojure -- which > would, of course, necessitate having the whole stack in RHEL/EPEL 6 as > well. Unless you have a really, really good reason to do it in Clojure I'd urge you to look into using something that is already available on RHEL/EPEL/Fedora. No? Read on then... > I noticed [a post by > Lubomir](http://article.gmane.org/gmane.linux.redhat.fedora.java/3458/) back > in 2010 asking for Maven packages to be made available in EPEL, but as > we just discovered today, Maven is still not available. There seems to > be no reply, at least on the mailing list, to that request.. There have been more than one requests before. The truth is however, that getting whole Maven stack into EPEL will require *substantial* time investment. Certainly not a 1-man job, and I assume there will be hard-to-identify bugs resulting from mixing of older RHEL java packages and requirements of new packages from Fedora. You will probably have to package additional packages for compatibility. > Is there any technical difficulty involved in making these packages > available on EPEL? If it's a lack of interest, Kushal and myself > hereby volunteer to be the ones in charge of doing the EPEL > maintenance work. Problem is that just figuring out those problems is sometimes non-trivial because the error messages suck most of the time. You *will* have to modify a lot of Java packages, such as your new reviews. It will mean longer and uglier spec files, so at least in my packages I'd prefer to keep those spec files separate. You will find that not all RPMs in Fedora correctly state their required versions for example. Or that some packages are named differently. Or that we have patches packages to work on JDK 7, so they don't work on JDK 6 anymore (we don't have it in Fedora anymore). Another issue is that current Maven was bootstrapped using older maven2 package. However we don't have that anymore and bootstrapping maven would have to be reworked from scratch. I would suggest making a list of maven dependency tree and have a look at the number of packages you'd need to package. If that doesn't scare you off, make a list of packages that are already in RHEL but different versions. Those might need compat packages. Also note that for example jakarta-commons-* packages have been renamed to apache-commons-*. In short: no one really tried to get Maven 3.x into EPEL because just figuring out scope of such task is non-trivial. There's too many unknowns in play there. I am also sorry to say that you are unlikely to receive much support from me (as Maven maintainer) and most probably some other Java folks. Not because we don't want to help, but because you will be facing issues we haven't seen and just to figure out what needs to be done would take too much of our time we'd rather spend working on improving Java packaging for the future. A paradox: you might get more help from some other distributions who had to go through bootstrapping Maven when they started using our Java stack. -- Stanislav Ochotnicky <sochotnicky@xxxxxxxxxx> Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
