public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Maven from source - version 2.x or 3.x ?
Date: Mon, 23 May 2011 00:54:02 +0300	[thread overview]
Message-ID: <4DD985FA.3020904@gentoo.org> (raw)
In-Reply-To: <4DD923B5.6060508@codelutin.com>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On 05/22/2011 05:54 PM, Eric Chatellier wrote:
> Le 22/05/2011 07:38, Kasun Gajasinghe a écrit :
>> Hi all,
>> I'm working on getting Apache Maven in to work by building from
>> source. Currently, in main tree, Maven is installed using the binary
>> (dev-java/maven-bin), which is against the Gentoo Java Packaging
>> Policy.
>>
>> Getting Maven in to work by building-from-source is a lengthy process.
>> We have two main versions to go ahead. The 2.x range with the latest
>> being v2.2.1, and the 3.x range with the latest being v3.0.3. The
>> compatibility notes for 2.x and 3.x are at [1]. There's only few
>> compatibility issues as I've seen. I was thinking to go with 2.x since
>> in my experience and the area where I was involved in, haven't had any
>> plans to migrate to Maven 3.x soon. But the overall picture may vary.
>>
>> So, I'm asking from the Gentoo's Java community, what's the suitable
>> version to go with? 2.x or 3.x
> Hi, i'm a gentoo user and java developper using maven for
> years. I also known the maven gentoo problem ;)
> So i'll be happy to help you or test your work.
> 
> For maven 2/3, 3.x is a new achitecture intended to
> be maven 2 complaint. So, i vote for 3.x.
> But maybe 3.x is too young...
> 

Eventually 2.x will die while 3.x continues to be supported and so on. I
would target 3.x and then do 2.x also if it's relative easy to backport.
If they are largely compatible as you say then targeting 3.x shouldn't
be a problem knowledge wise.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2011-05-22 21:55 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 [this message]
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                     ` [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=4DD985FA.3020904@gentoo.org \
    --to=betelgeuse@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