Brett,
If someone would agree to kindly grant me karma to update issue
titles, I'll change them for you.
Paul
On Thu, Aug 21, 2008 at 6:07 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> On 22/08/2008, at 8:20 AM, Paul Benedict wrote:
>
>> Well, before anyone begins doing 2.1 work, take the 3.0.
I think this particular release is the oddball with the changes being so
pervasive and taking so long. 2.0.9 went through the RCs in just a few
weeks. I don't think we need betas on point releases...really only on
things leading up to the .0 release.
-Original Message-
From: John Casey [ma
See MNG-3724
John Casey wrote:
I've got the fix on my machine, just testing to see what it does to
performance numbers.
-john
Daniel Kulp wrote:
John,
Performance is looking very good.My testcase that runs in 32secs
on 2.0.9 runs in 26sec with this RC. Very nice job.
However, there
I'm willing to try anything once, basically. I think we've had better
success with the release candidate approach than anything else to date,
but if we could find a way to make sure the odd point revision releases
could get the same attention, I think it'd be fine.
Maybe others will disagree,
I've got the fix on my machine, just testing to see what it does to
performance numbers.
-john
Daniel Kulp wrote:
John,
Performance is looking very good.My testcase that runs in 32secs on 2.0.9
runs in 26sec with this RC. Very nice job.
However, there seems to be a problem with it an
John,
Good response.
I am still interested in finding a way of spacing the release
candidates out. What would you think of if 2.0.10 was voted as beta,
and then 2.0.11 would take the place of RC1-RC10 build list. Once the
2.0.11 regression issues come in and are fixed, then you would have a
nice
I have different experiences from past releases of the Maven project. If
an issue comes up during a release vote, for instance, that brings up a
very valid point of whether it's really kosher to fix it and continue
the vote. Most people would say - and this is the general agreement in
Maven, I
I would like to mention that Niall Pemberton, owner of Common
Beanutils, had a very good experience doing the latest builds using
RC. Each time he published an RC, he waited about 4-6 weeks to collect
feedback, patched those bugs, and released the next RC.
Are shotgun release candidates too hurtfu
John,
Performance is looking very good.My testcase that runs in 32secs on 2.0.9
runs in 26sec with this RC. Very nice job.
However, there seems to be a problem with it and the eclipse plugin in a
reactor build. With the CXF build, run:
mvn test-compile eclipse:eclipse -Pnochecks -o
a
Hi again everyone,
I wanted to announce the availability of the latest release candidate,
2.0.10-RC10. You can grab it here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache/maven/apache-maven/2.0.10-RC10
I've closed the few issues that came out of RC9, and improved
Well for now we are locked out of Apache SVN. John already emailed infra
so now we wait for it to get unlocked.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2008 5:45 PM
To: Maven Developers List
Subject: Re: [WARNING] Continuous integration
Thanks.
I hope Dan will test it.
And I will start again the release process tomorrow.
--
Olivier
2008/8/22 Emmanuel Venisse <[EMAIL PROTECTED]>:
> It's ok.
>
> Emmanuel
>
> On Fri, Aug 22, 2008 at 11:48 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
>>
>> Patch applied and snapshot deploy.
>>
>> Mac
Nice.
As a french reader, I haven't found any typos ;-).
--
Olivier
2008/8/22 Benjamin Bentmann <[EMAIL PROTECTED]>:
> Hi,
>
> I would like to propose the following update (excluding typos ;-) ) to the
> index.apt template given in the Plugin Documentation Standard [0]:
>
>> * Usage
>>
>> Genera
+1 I like it!
jesse
On Fri, Aug 22, 2008 at 4:21 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Like a little "howto" read this documentation. I think it's good.
>
> +1
>
> On 22-Aug-08, at 2:46 AM, Benjamin Bentmann wrote:
>
>> Hi,
>>
>> I would like to propose the following update (excluding ty
Like a little "howto" read this documentation. I think it's good.
+1
On 22-Aug-08, at 2:46 AM, Benjamin Bentmann wrote:
Hi,
I would like to propose the following update (excluding typos ;-) )
to the index.apt template given in the Plugin Documentation Standard
[0]:
* Usage
General ins
Patch applied and snapshot deploy.
Mac users are welcome to test :-)
Just add the file svn-settings.xml (same as here [1] ) in ~/.scm/
Thanks,
--
Olivier
[1]
https://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/resource
Thanks a lot Brian,
It seems we have always an issue with credentials on subversion.
I'll try to see with Kohsuke if he has an idea where it can come from ..
cheers
arnaud
On Fri, Aug 22, 2008 at 5:29 AM, Brian E. Fox <[EMAIL PROTECTED]>wrote:
> It's upgraded to 1.249 now.
>
> -Origina
On Fri, Aug 22, 2008 at 1:54 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Be sure about my spare time is not 100% sure :-)
> Currently there are only 7 issues for 1.1.1 (some have patches).
>
> But it looks Mark has attached a patch to SCM-402 (I can certainly
> apply it quickly and rebuild a rel
I'll test it :)
Emmanuel
On Fri, Aug 22, 2008 at 11:10 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Ok I will apply the patch (I hope a mac user will test the fix :-) ).
>
> And restart the release process .
>
> --
> Olivier
>
> 2008/8/22 Olivier Lamy <[EMAIL PROTECTED]>:
> > Hi Emmanuel,
> > B
Ok I will apply the patch (I hope a mac user will test the fix :-) ).
And restart the release process .
--
Olivier
2008/8/22 Olivier Lamy <[EMAIL PROTECTED]>:
> Hi Emmanuel,
> Be sure about my spare time is not 100% sure :-)
> Currently there are only 7 issues for 1.1.1 (some have patches).
>
>
Hi Emmanuel,
Be sure about my spare time is not 100% sure :-)
Currently there are only 7 issues for 1.1.1 (some have patches).
But it looks Mark has attached a patch to SCM-402 (I can certainly
apply it quickly and rebuild a release process tomorrow).
WDYT ?
--
Olivier
2008/8/22 Emmanuel Veniss
Are you sure for the 1.1.1 date?
Emmanuel
On Fri, Aug 22, 2008 at 10:04 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Dan,
> I have already planned/think about a 1.1.1 (with bug fixes) 4/5 weeks
> after the 1.1.
> Can we wait this ??
>
> Thanks,
> --
> Olivier
>
>
> 2008/8/22 Mark Struberg <[EMA
My vote: +1
- Imran
On Fri, Aug 22, 2008 at 5:29 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> The last release of maven-scm is now 14 months old.
> I'd like to release maven-scm 1.1 which include two new providers git
> and accurev and fix some issues.
>
> We solved 26 issues :
> http://ji
Dan,
I have already planned/think about a 1.1.1 (with bug fixes) 4/5 weeks
after the 1.1.
Can we wait this ??
Thanks,
--
Olivier
2008/8/22 Mark Struberg <[EMAIL PROTECTED]>:
> For what I understand, this is a pure Apple/subversion problem, and has
> nothing to do with maven-scm.
>
> The only th
Great. No problems with our 40+ modules. A non-binding
+1
>From me.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Vincent Siveton
Gesendet: Freitag, 22. August 2008 14:53
An: Maven Developers List
Betreff: [VOTE] Release Maven Javadoc plugin ve
+1
Dan Fabulich wrote:
-- Forwarded message --
Date: Tue, 19 Aug 2008 13:00:19 -0700 (PDT)
From: Dan Fabulich <[EMAIL PROTECTED]>
Reply-To: Maven Developers List
To: Maven Developers List
Subject: [VOTE] Release Maven Invoker version 2.0.10
Hi,
This release is to prepare f
+1
Sent from my iPhone
On Aug 22, 2008, at 8:47 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
-- Forwarded message --
Date: Tue, 19 Aug 2008 13:00:19 -0700 (PDT)
From: Dan Fabulich <[EMAIL PROTECTED]>
Reply-To: Maven Developers List
To: Maven Developers List
Subject: [VOTE]
For what I understand, this is a pure Apple/subversion problem, and has nothing
to do with maven-scm.
The only thing we could do is to introduce a new parameter in the
maven-scm-provider-svn-commons/src/main/mdo/svn-settings.mdo
'useNonInteractive' which defaults to true.
Use this information
-0.
SCM-402 scm:checkin doesn't work on OS X 10.5 Leopard
http://jira.codehaus.org/browse/SCM-402
This breaks the release plugin on Leopard also. I'd mark it -1 if I
thought I had time to help fix it.
-Dan
Olivier Lamy wrote:
Hi,
The last release of maven-scm is now 14 months old.
I'd lik
+1
--
Olivier
2008/8/19 Dan Fabulich <[EMAIL PROTECTED]>:
> Hi,
>
> This release is to prepare for the release of Maven Reactor Plugin.
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14495
>
> There are still a couple of issues left
-- Forwarded message --
Date: Tue, 19 Aug 2008 13:00:19 -0700 (PDT)
From: Dan Fabulich <[EMAIL PROTECTED]>
Reply-To: Maven Developers List
To: Maven Developers List
Subject: [VOTE] Release Maven Invoker version 2.0.10
Hi,
This release is to prepare for the release of Maven R
Vincent Siveton schrieb:
> Hi,
>
> We solved more than 30 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14120&styleName=Html&projectId=11138
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=
Hi,
We solved more than 30 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14120&styleName=Html&projectId=11138
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1
Staging repo:
http://people.apache.o
Hi,
I'd like to release the maven-dependency-tree shared component version
1.2. This release is required by m2eclipse and fixes a number of
bugs.
Staging repo:
http://people.apache.org/~markh/staging-repo/
Staging site (wait for the sync):
http://maven.apache.org/shared/maven-dependency-tree-1.
Olivier Lamy schrieb:
> Hi,
> The last release of maven-scm is now 14 months old.
> I'd like to release maven-scm 1.1 which include two new providers git
> and accurev and fix some issues.
>
> We solved 26 issues :
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&styleName=Html&pro
+1
LieGrue,
strub
--- Olivier Lamy <[EMAIL PROTECTED]> schrieb am Fr, 22.8.2008:
> Von: Olivier Lamy <[EMAIL PROTECTED]>
> Betreff: [VOTE] Release Maven Scm 1.1 (take 2)
> An: "Maven Developers List" , [EMAIL PROTECTED]
> Datum: Freitag, 22. August 2008, 13:29
> Hi,
> The last release of maven
Hello,
I have written a custom Maven2 plugin, in our CVS repo called
maven2.plugin. In the POM, I have specified the goalprefix to be
"telenet". However, in the generated site, all my goals are listed as:
2.:
Is there still a known bug that this goalprefix is not correctly picked
up for the sit
Hi,
The last release of maven-scm is now 14 months old.
I'd like to release maven-scm 1.1 which include two new providers git
and accurev and fix some issues.
We solved 26 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&styleName=Html&projectId=10527&Create=Create
Staging
Hi,
I would like to propose the following update (excluding typos ;-) ) to
the index.apt template given in the Plugin Documentation Standard [0]:
* Usage
General instructions on how to use the Plugin Name can be found on the
{{{usage.html}usage page}}. Some more
specific use cases are d
I'm about to leave for Phuket for a few days, will follow up on this
when I get back. I'd like to get this sorted... so folks stop
complaining about them being broken ;-)
--jason
On Aug 20, 2008, at 2:53 PM, Raphaël Piéroni wrote:
Hi Jason,
To have gmaven archetypes in the internal cata
On Aug 20, 2008, at 11:35 AM, Jason van Zyl wrote:
Do your archetypes refer to repositories that you defined?
Not sure what you mean... :-\
--jason
On 19-Aug-08, at 8:36 PM, Jason Dillon wrote:
Hiya, I'm getting lots of user reports of problems using the GMaven
archetypes... could be my
That has to be randomness in your test timings, assuming you didn't use
the new command line arguments. At best my changes should have no
positive effect on performance. :-)
-Dan
Ralph Goers wrote:
Well, I didn't really look at what you did, but I noticed that it did improve
my test times a
42 matches
Mail list logo