Thanks - that worked a treat. One other thing - *why* does it work in a forked JVM and not in the same one Maven is running in?
-- Anthony Roy. t: 01937 54 (6003) e: [EMAIL PROTECTED] The British Library Boston Spa Wetherby West Yorkshire LS23 7BQ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 28 July 2005 13:17 To: Maven Users List Subject: Re: [M1]: Log4J and jUnit not playing together properly... Hi, Try to set this property in your project.properties file. maven.junit.fork=yes Damien Viel Selon "Roy, Anthony" <[EMAIL PROTECTED]>: > Hi all, > > I have added logging using log4j to a new project, and cannot get the > unit tests working properly. Maven doesn't seem to be able to find the > log4j.properties file - I keep getting the warning: > > [junit] Running uk.bl.bspa.oclc.retrieval.dispatch.FTPUploaderTest > log4j:WARN No appenders could be found for logger > (uk.bl.bspa.util.config.ClassInfo). > log4j:WARN Please initialize the log4j system properly. > > After this I get ExceptionInInitializerError's thrown for the classes > with logging that are called by the tests. > > Any ideas on where log4j.properties should be, or whether there are > properties that need setting in the project.properties or project.xml? > I have the path to log4j.properties included in the > <unitTest><resources> section of the POM. > > Thanks, > > -- > Anthony Roy. > > t: 01937 54 (6003) > e: [EMAIL PROTECTED] > > The British Library > Boston Spa > Wetherby > West Yorkshire > LS23 7BQ > > > > > -----Original Message----- > From: Michael Owen [mailto:[EMAIL PROTECTED] > Sent: 28 July 2005 12:07 > To: [email protected] > Subject: [M1] Clover license problem + cxclude certain files from clover > > > (Using Maven 1.0.2) > > Hi, > > Problem1: > > I need to define where the license is using: > > maven.clover.license.path=C://clover/licenses/clover.license > > however, I want this to work across many peoples machines (windows + > linux), and therefore having this file path is "bad". I thought about > using an environment variable (ie. > maven.clover.license.path=${CLOVER_FOLDER}/licenses/clover.license), > however, been told that property files can't access environment > variables. > Then thought about using an intranet, and let the license be got at from > > something like > maven.clover.license.path=http://companyintranet:8888/clover > (snip) etc. etc., however, it didn't like this either. > > Any ideas? > > Problem2: > > I need to exclude certain files from being included in the coverage > calculation when using the clover plugin 1.3_01. The > maven.clover.excludes > property didn't come in until clover 1.7. Any ideas on the best way, > while > still using the same plugin? > > I'm thinking about moving files I don't what to be included in the > coverage into another folder, and then moving back after the coverage > calculation, > however, this seems a hack. > > Many thanks, > > Mike > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ********************************************************************** > **** > > Experience the British Library online at www.bl.uk > > Help the British Library conserve the world's knowledge. Adopt a Book. > www.bl.uk/adoptabook > > ********************************************************************** > **** > > The information contained in this e-mail is confidential and may be > legally privileged. It is intended for the addressee(s) only. If you > are not the intended recipient, please delete this e-mail and notify > the [EMAIL PROTECTED] > : The contents of this e-mail must not be disclosed or copied without the > sender's consent. > > The statements and opinions expressed in this message are those of the > author and do not necessarily reflect those of the British Library. > The British Library does not take any responsibility for the views of > the author. > > ********************************************************************** > **** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
