I did this for surefire itself, and the plugin. IMO, this is stable now
(all the bugs in JIRA were problems in the old surefire as well), and is
much improved (better error reporting, output, testng support and memory
leak fixed).
There are still 10 issues to fix before the final release. Any
So this afternoon, the latest surefire snapshot landed and began to
politely request that I update my dependency to TestNG 4.7 instead of
4.6.1 for TestNG support. Wishing to build, I did so.
TestNG 4.7 isn't up on central, though, so I installed it in ~/.m2/
repository. That was a manual pr
sure, I wasn't able to find it.
On 4/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Maybe we should just remove this and use commons-lang?
- Brett
[EMAIL PROTECTED] wrote:
> Author: carlos
> Date: Sun Apr 30 12:59:22 2006
> New Revision: 398419
>
> URL: http://svn.apache.org/viewcvs?rev=398419
Kenney,
Just a brief response - I agree totally that adding a element
to the dependency element is the best way to go for this. It was a
really a bad oversight on my part that I didn't add that in 2.0.
I don't think you can activate them in the way you've described right
now as profiles in
ok, see now that the issue was closed.
I'm not sure how you see the "old style" tests as cleaner. What makes
the new ones less clean in your opinion? The IT's are certainly not unit
tests (the plugin framework tests are only just barely units
themselves), and significantly slower to run.
- B
Maybe we should just remove this and use commons-lang?
- Brett
[EMAIL PROTECTED] wrote:
Author: carlos
Date: Sun Apr 30 12:59:22 2006
New Revision: 398419
URL: http://svn.apache.org/viewcvs?rev=398419&view=rev
Log:
Fix package names
Modified:
maven/sandbox/jdk13-util/src/main/java/org/ap
[EMAIL PROTECTED] wrote:
Author: kenney
Date: Sun Apr 30 15:01:04 2006
New Revision: 398452
URL: http://svn.apache.org/viewcvs?rev=398452&view=rev
Log:
Added testcase for MRESOURCES-18. This should really go into
the resources-plugin itself using the new framework, but
committing anyway for fut
On Sun, 30 Apr 2006, Alexandre Poitras wrote:
[crossposted to dev: proposal near end]
First of all, Maven provides an flag per dependency. Users of
a project declaring those dependencies will need to add any
optional dependencies that they might need themselves.
I agree, it's a little bit more v
On 28 Apr 06, at 11:06 AM 28 Apr 06, Kenney Westerhof wrote:
On Fri, 28 Apr 2006, Brett Porter wrote:
For people not using IntelliJ this doesn't work.
Eclispe has 3 default tags:
XXX - severe problem, but might work in some/most cases
FIXME - indicates a workaround/too simple solution and sho
