Jason van Zyl wrote:
Correct me if I'm wrong here Benjamin but I think he's talking about
stating what tests you want to run, and how they are grouped
declaratively. As a best practice don't use suites and come up with a
way in Surefire to group things and avoid grouping of things in code.
I
Fabrizio found a last-minute bug. I've rolled a new candidate. Let's
vote again!
[Boy, the temptation to let the rules slide on a change this small is
almost irresistable. ;-)]
-Dan
-- Forwarded message --
Date: Sat, 26 Jan 2008 11:53:28 -0800 (Pacific Standard Time)
From
Fabrizio Giustina wrote:
while testing this I found http://jira.codehaus.org/browse/SUREFIRE-444
I verified that the bug was still in 2.4 and I am not sure how many
users can be affected... since it can breaks builds without providing
any useful information about the cause I'd like it to be incl
If it's all in maven-artifact it's already being done. And the same
profile I suppose we could use it everywhere. The retro stuff seems
stable and workable.
On 27-Jan-08, at 3:20 PM, Brian E. Fox wrote:
Is it absolutely required to use 1.5? If there's a good way to work
around it, we should
and I don't think 2.1 has any kind of firm release date planned
jesse
On Jan 27, 2008 5:29 PM, Don Brown <[EMAIL PROTECTED]> wrote:
> Using Java 1.4 will require using the backport of the concurrent
> utils, which according to Jason, had some difficulty working with the
> 2.0 stable branch. Als
Using Java 1.4 will require using the backport of the concurrent
utils, which according to Jason, had some difficulty working with the
2.0 stable branch. Also, considering the incompatibility of
commons-logging with some plugins, the http wagon should probably only
go into the 2.1 branch.
So, if
+1
Dan Fabulich wrote:
With a change as big as Surefire 2.4, there turned out to be a few bugs
still lurking.
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=14016
There are still 38 issues left in JIRA:
http://jira.codehaus.org
Is it absolutely required to use 1.5? If there's a good way to work
around it, we should aim for 2.0.9
-Original Message-
From: Don Brown [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 27, 2008 4:49 PM
To: Maven Developers List
Subject: Re: Dramatically speed up dependency resolution
On
On 1/28/08, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> > * Connection pooling: Uses the http wagon instead of http-lightweight
> > and fixed incorrect http client initialization
>
> James Dumay also worked on this. So you might want to talk to him or
> look. I'm not sure if you're the Don Brown fro
+1
Arnaud
On Jan 27, 2008 8:29 PM, Milos Kleint <[EMAIL PROTECTED]> wrote:
> +1
>
> Milos
>
> On Jan 26, 2008 8:53 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> >
> > With a change as big as Surefire 2.4, there turned out to be a few bugs
> > still lurking.
> >
> > We solved 7 issues:
> >
> http
+1
Milos
On Jan 26, 2008 8:53 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> With a change as big as Surefire 2.4, there turned out to be a few bugs
> still lurking.
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=14016
>
> There
I looked it over, and after a chat on IRC I'm cool with it being merged.
+1
On 27-Jan-08, at 5:31 AM, Milos Kleint wrote:
Hello,
I would like to integrate the toolchains proposal into current trunk.
http://docs.codehaus.org/display/MAVEN/Toolchains
There are multiple steps towards the final g
On 27-Jan-08, at 5:31 AM, Milos Kleint wrote:
Hello,
I would like to integrate the toolchains proposal into current trunk.
http://docs.codehaus.org/display/MAVEN/Toolchains
There are multiple steps towards the final goal.
1. move the internal components from shared/ to components/ and make
it
On 27-Jan-08, at 3:06 AM, Don Brown wrote:
One of my pain points with Maven is how slow it is to "download the
internet", so rather than bitch (or more accurately, continue
bitching), I decided to do something about it. I created a customized
build of Maven 2 (MNG-3379, WAGON-98) that, at leas
Awesome, go for it.
+1
On 26-Jan-08, at 11:53 AM, Dan Fabulich wrote:
With a change as big as Surefire 2.4, there turned out to be a few
bugs still lurking.
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=14016
There are still 3
On 25-Jan-08, at 5:22 PM, Carlos Sanchez wrote:
great, but
- who is going to enforce it?
- who is going to say what the right pom is for a project that doesnt
build with Maven?
If someone from a project submits a POM then we should take that. If
projects don't then we take a submission fro
Hello,
I would like to integrate the toolchains proposal into current trunk.
http://docs.codehaus.org/display/MAVEN/Toolchains
There are multiple steps towards the final goal.
1. move the internal components from shared/ to components/ and make
it part of default core distribution. It shall be pa
One of my pain points with Maven is how slow it is to "download the
internet", so rather than bitch (or more accurately, continue
bitching), I decided to do something about it. I created a customized
build of Maven 2 (MNG-3379, WAGON-98) that, at least in my simple
tests, cut the dependency resolu
+0
while testing this I found http://jira.codehaus.org/browse/SUREFIRE-444
I verified that the bug was still in 2.4 and I am not sure how many
users can be affected... since it can breaks builds without providing
any useful information about the cause I'd like it to be included as
soon as possible
19 matches
Mail list logo
