From: "Jörg Schaible" <joerg.schaible@gmx.de>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Re: Re: Maven from source - version 2.x or 3.x ?
Date: Thu, 26 May 2011 18:18:19 +0200 [thread overview]
Message-ID: <irlugb$tu8$1@dough.gmane.org> (raw)
In-Reply-To: BANLkTimVfzXBW-sp5LtqcWwwX3a8QjoEiw@mail.gmail.com
Kasun Gajasinghe 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?
For Java: Yes. Use flags are still useful for dropping optional deps. I
recommended that already years ago.
>> 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.
>
> If any of you is interested, you are welcome to have a look at the
> proposal for Maven from source for Gentoo [1]. Feedback is much
> appreciated.
>
> [1]
>
[http://socghop.appspot.com/gsoc/proposal/review/google/gsoc2011/kasun_gajasinghe/1
One hint only: You might take a closer look at Tycho. That one replaces the
default dependency mechanism with a DependencyResolver that reads the
dependencies from the OSGi entries in the manifest and uses a complete
different repo layout (more or less what you see, when you look into
Eclipse's plugins directory). It might be possible to develop a solution
that uses similar hooks into the Maven core - to resolve deps and to support
a different repo layout. However, that requires a Gentoo-version of Maven
...
- Jörg
next prev parent reply other threads:[~2011-05-26 16:19 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
2011-05-26 16:18 ` Jörg Schaible [this message]
2011-05-26 16:25 ` [gentoo-java] " 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='irlugb$tu8$1@dough.gmane.org' \
--to=joerg.schaible@gmx.de \
--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