Um, JDK 1.5 isn't yet the "current release" of Java. It's still only
beta.
On Mon, 2004-07-26 at 13:59, Malachi de AElfweald wrote:
> Thanks to everyone for their help... Adding those two properties (either
> -D or project.properties) fixed the problem.
>
>
> A couple thoughts/comments
>
maven.junit.fork=true
>
> Emmanuel
>
> - Original Message -
> From: "Scott Brickner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, December 29, 2003 11:00 PM
> Subject: Can I suppress the junit output?
>
>
> >
How can I fix things so I don't get the 5+ lines of output on the
console for every single testcase?
I really only want to know when a test fails. The xml reports are fine
for when I'm building the site, but 99% of the time I'm building during
new development and just want failing testcases.
In m
On Wed, 2003-12-17 at 15:16, Emmanuel Venisse wrote:
> Plugin is released. You can download it.
>
> Emmanuel
Great. This looks to be working now. Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
maven-jcoverage-plugin-1.0.1 (seems to happen with 1.0, too)
On Wed, 2003-12-03 at 15:04, Emmanuel Venisse wrote:
> What's you jcoverage plugin version?
>
> Emmanuel
>
> - Original Message -----
> From: "Scott Brickner" <[EMAIL PROTECTED]>
> To: &l
I just added the jcoverage report to my project and it's not running
right. Has anyone seen this before? The actual text referenced in the
exception is "\357\277\275".
The output of the JCoverage task is below...
jcoverage 1.0.5 copyright (c)2003 jcoverage ltd. http://jcoverage.com/
jcoverage is
On Wed, 2003-11-12 at 03:28, Martin Skopp wrote:
> IMHO this is a bug in the shell-script MAVEN_HOME/bin/maven
>
> Change the lines containing
>
> $MAIN_CLASS $@
>
> into
>
> $MAIN_CLASS "$@"
>
> Well after all, this probably depends upon the actual shell you are
> using. I don't
On Sun, 2003-11-09 at 01:40, [EMAIL PROTECTED] wrote:
> placing the log in ~/.maven makes sense, except when you run multiple
> mavens simultaneously.
Placing it in the current working directory doesn't make any more sense.
The --find option lets you run maven from pretty much anywhere in your
pr
something does go wrong (or if I ask for a higher-than-normal level of
verbosity).
On Sat, 2003-11-08 at 09:41, Jim Crossley wrote:
> Hi Scott
>
> Scott Brickner <[EMAIL PROTECTED]> writes:
>
> > Maven is littering my project folders with maven.log files, none of
> >
Maven is littering my project folders with maven.log files, none of
which say anything useful (just info on the running time). Is there some
officially supported way for me to make it put that log somewhere else?
Or to suppress it entirely when things are running fine?
---
10 matches
Mail list logo
