In one of my builds (run via Hudson), on only one of the multiple slaves it
could run on, I'm seeing the below error. I've had the machine rebooted, but
it keeps coming back. The other slaves this build runs on are configured
identically to this one, and, as I mentioned, they have no problems. Any
I've run into the same problem with Cobertura and Spring - what seemed to
fix it was, in the context file, changing aop:config to aop:config
proxy-target-class=true. I'm not entirely sure *why* that worked (I dealt
with this a couple months ago, and it required a *lot* of googling to get
any kind
Hi -
I'm working on transitioning a large multi-module project from Ant to Maven,
and have encountered a truly bizarre use case for Surefire. The unit tests
in a number of the modules use a fairly elaborate Junit runner framework
developed here - logging, configuration file locations, etc are all
Whoops - left off classpath from the subject.
A.
On Fri, May 1, 2009 at 1:27 PM, Andrew Bayer andrew.ba...@gmail.com wrote:
Hi -
I'm working on transitioning a large multi-module project from Ant to
Maven, and have encountered a truly bizarre use case for Surefire. The unit
tests
/configuration
Kalle
PS. And you know you can look at our poms if you like...
On Fri, May 1, 2009 at 2:21 PM, Andrew Bayer andrew.ba...@gmail.com
wrote:
Whoops - left off classpath from the subject.
A.
On Fri, May 1, 2009 at 1:27 PM, Andrew Bayer andrew.ba...@gmail.com
wrote
Hi all -
I'm working on moving a sizeable multimodule project from Ant to Maven, and
have, along the way, run into a number of annoying circular dependency
problems. This project was set up using some custom Ant tasks/targets for
inter-module dependency management and unit testing, which worked
Ah-ha - that would do the trick. I knew there'd be something fairly obvious
I was missing. =)
A.
On Fri, Apr 24, 2009 at 10:40 AM, Stan Devitt sdev...@rim.com wrote:
Can you move D to A and use an assembly to build the external jar you
want?
Hi -
I've got a sprawling and unpleasant source tree that I'm moving into a
Maven-based build, using the reactor to call each of the many sub-projects.
I just want to clarify exactly how the reactor finds sub-projects - does it
only look in the first level of subdirectories below the basedir
it to **/project.xml instead.
-Original Message-
From: Andrew Bayer [mailto:[EMAIL PROTECTED]
Sent: 26 March 2004 17:03
To: [EMAIL PROTECTED]
Subject: Quick reactor question
Hi -
I've got a sprawling and unpleasant source tree that
I'm moving into a
Maven-based build, using
