public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Generation of ebuilds with maven build system
Date: Wed, 31 Aug 2016 08:09:48 +0900	[thread overview]
Message-ID: <871t15lupv.fsf@gentoo.org> (raw)

Hi,

I am interested in packaging spark (bug 523412).  By default maven tries
to download 2.5GiB dependencies into my $HOME.  Spark is large and has a
lot of dependencies.  I bet converting the maven build system of spark
into a manual one[1] will be too complex.

In the mean time, I stepped upon java-ebuilder[2] for creating ebuilds
by parsing pom.xml.  I am maintaining the R overlay[3], which generates
10000+ ebuilds from R package repositories such as CRAN, BIOC, etc.
Similarly, g-sorcery[6] can be used to generate pypi (for python), elpa
(for emacs) ebuilds and overlays.  This is a good packaging model to
deal with large language-specific repositories and ecosystems.

What is the status of java-ebuilder, and is there an example for how to
use it?

maven has 153861 artifacts[4], making manually packaging for Gentoo
impossible.  How about using java-ebuilder to generate ebuilds from the
maven repository and expose them with java overlay[5]?  What do you say?

Cheers,
Benda

1. https://wiki.gentoo.org/wiki/Gentoo_Java_Packing_Policy#Maven
2. https://gitweb.gentoo.org/proj/java-ebuilder.git
3. layman -i R_Overlay
4. http://search.maven.org/#stats
5. layman -i java
6. https://github.com/jauhien/g-sorcery


             reply	other threads:[~2016-08-30 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 23:09 Benda Xu [this message]
2016-10-02 20:44 ` [gentoo-java] Generation of ebuilds with maven build system Harald Weiner
2016-10-19  5:15   ` Austin English
2016-10-21  1:24     ` Benda Xu
2016-10-28 16:29       ` Harald Weiner
2016-10-29  8:52         ` Benda Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t15lupv.fsf@gentoo.org \
    --to=heroxbd@gentoo.org \
    --cc=gentoo-java@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox