When I was puttering in JXR, Hervé mentioned that Vincent had a load
of stuff in a branch. Now that the new parent POMs are out, I'd like
to update JXR to use them, and make the plugin 'parent' to the general
plugin parent. Vincent, do you want to merge in your branch, first?
-
+1
On 18 August 2011 16:05, Kristian Rosenvold
wrote:
> Hi,
>
> The main intention of this release is to get java7 file attribute api's
> in use, which can be a great performance improvment for java7 mac &
> linux users. There should also be some improvement for 1.5/1.6 users,
> and this release
+1
Hervé
Le jeudi 18 août 2011, Kristian Rosenvold a écrit :
> Hi,
>
> The main intention of this release is to get java7 file attribute api's
> in use, which can be a great performance improvment for java7 mac &
> linux users. There should also be some improvement for 1.5/1.6 users,
> and this
+1
-Robert
> Date: Sat, 20 Aug 2011 21:56:08 +0100
> From: strub...@yahoo.de
> Subject: Re: [VOTE] Release Maven Jar Plugin version 2.3.2 and maven-archiver
> version 2.4.2
> To: dev@maven.apache.org
>
> +1
>
> LieGrue,
> strub
>
> --- On Sat, 8/20/11, Olivier Lamy wrote:
>
> > From: Ol
+1
LieGrue,
strub
--- On Sat, 8/20/11, Olivier Lamy wrote:
> From: Olivier Lamy
> Subject: Re: [VOTE] Release Maven Jar Plugin version 2.3.2 and maven-archiver
> version 2.4.2
> To: "Maven Developers List"
> Date: Saturday, August 20, 2011, 8:48 PM
> +1
>
> 2011/8/18 Kristian Rosenvold :
>
+1
2011/8/18 Kristian Rosenvold :
> Hi,
>
> The main intention of this release is to get java7 file attribute api's
> in use, which can be a great performance improvment for java7 mac &
> linux users. There should also be some improvement for 1.5/1.6 users,
> and this release is java 1.5+.
>
> The
3/4 weeks ago we should/may have done a release of 3.0.4 with existing
Aether/Sisu dependencies (thus yes existing ones are from Sonatype but are
dual licensed ASL/EPL - or maybe full ASL I don't remember).
Arnaud
On Fri, Aug 19, 2011 at 4:07 PM, Anders Hammar wrote:
> Arnaud, are you talking a
lø., 20.08.2011 kl. 09.50 +0930, skrev Barrie Treloar:
> On Fri, Aug 19, 2011 at 5:01 PM, Kristian Rosenvold
> wrote:
> [del]
> > After some time with git you just start using branches for "anything you
> > feel like", and imposing that kind of constraint now seems strange. So I
> > bring that bac
Only that the majority of users will get just get "unable to resolve artifact"
errors, and probably never know that they can update aether - which, whilst it
isn't a difficult thing to do is just a bit fiddly - instead they'll just get
frustrated that once again "maven black magic sucks".
If ro
Sorry Mark, exactly this solution has explicitly been vetoed with the vast
majority of -1 because of various other reasons.
If we release 3.0.4 now, a user might still update his local maven installation
to 1.12 easily. So I see no downside to the current status quo.
LieGrue,
strub
--- On Sat,
Please - for the love of ANY Maven user - please do NOT roll a 3.0.4 with any
Aether thats NOT 1.12.
1.11 that ships with the current Maven 3.0.3 has fundamental issues with your
local repository has artifacts from both mirrors and non-mirrors. I'm finding
more and more users getting hit with
11 matches
Mail list logo
