April 02, 2009 9:10 AM
> To: Maven Users List
> Subject: Re: strange error with hopefully easy solution?
>
> Hi Martin,
>
> you had me worried there for a moment, thought I'd emailed the wrong
> list!
>
> But anyway, I'll be surprised if you can reproduce it un
t any
liability for the content provided.
> Date: Thu, 2 Apr 2009 18:09:30 +0100
> From: adam.ma...@cyberspaceroad.com
> To: users@maven.apache.org
> Subject: Re: strange error with hopefully easy solution?
>
> Ah, the penny has finally dropped!
>
> The TestRunManager
this before, surefire trying to instantiate all my
classes, including inner classes.
-- Bryan
-Original Message-
From: Adam Hardy [mailto:adam.ma...@cyberspaceroad.com] Sent:
Thursday, April 02, 2009 9:10 AM
To: Maven Users List
Subject: Re: strange error with hopefully easy solution?
yberspaceroad.com]
Sent: Thursday, April 02, 2009 9:10 AM
To: Maven Users List
Subject: Re: strange error with hopefully easy solution?
Hi Martin,
you had me worried there for a moment, thought I'd emailed the wrong
list!
But anyway, I'll be surprised if you can reproduce it unless I
Wayne Fay on 02/04/09 17:10, wrote:
so the TestRunManagerTest$1 is obviously the result of jdk1.6.0_12 messing
up the compilation, right?
Run that $1 class thru JAD and see what the source code looks like.
You do know where $1 files usually come from, right (anonymous inner
classes) so this is
to:adam.ma...@cyberspaceroad.com]
Sent: Thursday, April 02, 2009 9:10 AM
To: Maven Users List
Subject: Re: strange error with hopefully easy solution?
Hi Martin,
you had me worried there for a moment, thought I'd emailed the wrong
list!
But anyway, I'll be surprised if you can reproduce it
> so the TestRunManagerTest$1 is obviously the result of jdk1.6.0_12 messing
> up the compilation, right?
Run that $1 class thru JAD and see what the source code looks like.
You do know where $1 files usually come from, right (anonymous inner
classes) so this is not necessarily an error. But it ma
lty reproducing this error
can you supply
pom.xml?
any plugins (junit-test-gen/batchrun) you may be using ?
empty org.permacode.patternrepo.basic.TestRunManagerTest Java class?
Date: Thu, 2 Apr 2009 14:26:32 +0100
From: adam.ma...@cyberspaceroad.com
To: users@maven.apache.org
Subject: str
binding effect. Given
that e-mails can easily be subject to manipulation, we can not accept any
liability for the content provided.
> Date: Thu, 2 Apr 2009 14:26:32 +0100
> From: adam.ma...@cyberspaceroad.com
> To: users@maven.apache.org
> Subject: strange error with hopefully e
My search results showed nothing in google or anything relevant in the archives,
but I have an intractable error in my test batchrun, which seems to be a
compilation problem.
The test is fine when executed in isolation.
This is what happens when I run all my test with "mvn clean test":
Tests
10 matches
Mail list logo
