On Fri, 2004-01-16 at 14:13, Vincent Massol wrote:
> *sigh*. The properties file I had attached got deleted (I really need to
> contact someone about the setting of this mailing list for
> attachements).
> 
> Try:
> http://cvs.apache.org/~vmassol/logging_client.properties.sample
> http://cvs.apache.org/~vmassol/logging_server.properties.sample

Okay. I checked out cactus and got it to compile. Headed into
./integration/maven and ran "maven", but I'm not sure what to do next to
test this.  Presumable copy something to somewhere?

Keith

> -Vincent
> 
> > -----Original Message-----
> > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > Sent: 16 January 2004 23:11
> > To: 'Cactus Users List'
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: cactus maven plugin and resources
> > 
> > Hi Keith,
> > 
> > I've just added basic logging support to the Cactus plugin for you :-)
> > 
> > The changes are in CVS HEAD for now (I'm doing a nightly build which
> > should be ready in about 1 hour).
> > 
> > You have to specify 2 properties: cactus.logging.config.client and
> > cactus.logging.config.server. They need to point to logging properties
> > files. I've attached 2 examples (you'll need to replace the
> @target.dir@
> > by the real location).
> > 
> > I haven't tested it yet. I'd be happy if you could verify if it works.
> > 
> > Thanks
> > -Vincent
> > 
> > > -----Original Message-----
> > > From: Keith Irwin [mailto:[EMAIL PROTECTED]
> > > Sent: 16 January 2004 22:03
> > > To: Cactus Users List
> > > Subject: cactus maven plugin and resources
> > >
> > > Folks--
> > >
> > > Kind of a best practices question:
> > >
> > > For unit tests, I'd like to include log4j.props and
> > > commons-logging.props to debug the test apparatus and to squelch
> those
> > > annoying warnings if you don't.
> > >
> > > However, I don't want these files in standard app builds (because
> > > there's some other framework thing going on).
> > >
> > > So, I've added the resources to the <unitTest/> element such that
> the
> > > files in question are included with regular unit test builds.
> > >
> > > However, the cactus unit test plugin seems to ignore this.
> > >
> > > Is there a preferred way to get this to work, or should I just
> create
> > a
> > > preGoal for cactus:test and cactus:match (the ones I regularly use)
> to
> > > copy the files over somehow?
> > >
> > > Thanks,
> > >
> > > Keith
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > 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]

Reply via email to