jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@pivolis.com>
Subject RE: cactus maven plugin and resources
Date Fri, 16 Jan 2004 22:10:51 GMT
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.


> -----Original Message-----
> From: Keith Irwin [mailto:keith@keithirwin.com]
> 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
> preGoal for cactus:test and cactus:match (the ones I regularly use) to
> copy the files over somehow?
> Thanks,
> Keith
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message