public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Burrell Donkin <robertburrelldonkin@gmail.com>
To: Gentoo Java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Re: Maven from source - version 2.x or 3.x ?
Date: Thu, 26 May 2011 11:58:18 +0100	[thread overview]
Message-ID: <BANLkTi=-XmM7-6S8QiDnL5WEq6T3sAJkfA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimVfzXBW-sp5LtqcWwwX3a8QjoEiw@mail.gmail.com>

On Thu, May 26, 2011 at 10:06 AM, Kasun Gajasinghe <kasunbg@gmail.com> wrote:
> Hi Jörg, and Robert,
>
>>> FWIW one unresolved challenge for linux distributions with the rise of
>>> bytecode languages (such as Java) is that compressed bytecodes are not
>>> binaries in the usual sense (platform dependent machine executable
>>> machine code). i know that it's a hard thing for the linux community
>>> to hear but it's about time that the community acknowledged that these
>>> languages are now mainstream and stop trying to force them into a
>>> inappropriate provisioning model.
>
> So... what exactly are you suggesting? Switch in to using binaries
> instead of building from source paradigm?

i love the "build-from-source" paradigm but dependencies for languages
such as Java are distributed as compressed intermediate bytecode
source not binaries. bytecode dependencies work quite differently from
the libraries used by directly compiled languages. building
applications in a reliable and reproducable way for bytecode languages
requires provisioning libraries in native source form (ie. bytecode).

it's time to start working with these new languages rather than try to
fight them by forcing them to fit into inappropriate structures.

>> To build Maven from source in Gentoo I wonder about the hen-and-egg problem.
>
> Yes. To Bootstrap maven, the work around for this is by: first
> generate ANT build.xml via `mvn ant:ant`. maven-bin will provide the
> mvn command in this case. Then patch that build.xml to the source.
> After that, ANT will take care of the building from source.

not very reliable :-/

- robert



  reply	other threads:[~2011-05-26 10:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22  5:38 [gentoo-java] Maven from source - version 2.x or 3.x ? Kasun Gajasinghe
2011-05-22  7:38 ` [gentoo-java] " kiorky
2011-05-22 14:54 ` [gentoo-java] " Eric Chatellier
2011-05-22 21:54   ` Petteri Räty
2011-05-23  6:15     ` Kasun Gajasinghe
2011-05-23  6:38       ` Petteri Räty
2011-05-23 16:52         ` Kasun Gajasinghe
2011-05-24  9:07           ` Petteri Räty
2011-05-24 11:52             ` Kasun Gajasinghe
2011-05-25 14:33               ` Robert Burrell Donkin
2011-05-25 16:09                 ` [gentoo-java] " Jörg Schaible
2011-05-26  8:44                   ` Robert Burrell Donkin
2011-05-26 15:57                     ` [gentoo-java] " Jörg Schaible
2011-05-26  9:06                   ` [gentoo-java] " Kasun Gajasinghe
2011-05-26 10:58                     ` Robert Burrell Donkin [this message]
2011-05-26 16:18                     ` [gentoo-java] " Jörg Schaible
2011-05-26 16:25                       ` Jörg Schaible
2011-05-26 11:10                   ` [gentoo-java] " Robert Burrell Donkin
2011-05-26 16:06                     ` [gentoo-java] " Jörg Schaible

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='BANLkTi=-XmM7-6S8QiDnL5WEq6T3sAJkfA@mail.gmail.com' \
    --to=robertburrelldonkin@gmail.com \
    --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