You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Keith Irwin <ke...@keithirwin.com> on 2004/01/16 22:03:13 UTC
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
RE: cactus maven plugin and resources
Posted by Keith Irwin <ke...@keithirwin.com>.
Vince--
I can't compile cactus. Seems it's looking for j2ee-13.jar from
.maven/repository/j2ee/jar but, alas, I don't have that and neither does
ibiblio.
Should I point at a different repository?
Keith
On Fri, 2004-01-16 at 14:10, Vincent Massol wrote:
> 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: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
> 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: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
>
>
> ______________________________________________________________________
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
RE: cactus maven plugin and resources
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Keith F Irwin [mailto:keith@keithirwin.com]
> Sent: 17 January 2004 22:59
> To: 'Cactus Users List'
> Subject: RE: cactus maven plugin and resources
>
> Vincent--
>
> Re: log resources for cactus runs only...
>
> I snagged the code out of CVS this morning, hunted down all the
> dependencies, created build.properties, and produced the two jars, ran
> the maven plugin install, copied the jars into the repository, and
> removed all the other jars (just to see) and even changed my
> project.xml.
>
> Maven insists on downloading a 2003 version of the 1.6dev branch
(maybe
> for some other issue), but now I get an aspectj error. (See
postscript
> below.)
I think I know. You need to understand that maven downloads the
dependencies defined in project.xml. If it doesn't find them locally it
will try to fetch them onsite from ibiblio. My guess is you may have
made an error in renaming the jars, so that the name doesn't match the
one defined in the plugin's project.xml.
>
> I do remember that when building, I got a "can't find aspectj.jar"
even
> though it seems to be on every path.
That's not a problem. I get it too.
>
> I'll see if I can track that down.
>
> Meanwhile, how do I know if my project/maven is using the "new" plugin
> jars? (I'd like to be able to report that it worked or didn't work
> based on the right code. ;)
I don't understand the term "plugin jars". A plugin is a jar, there is
only one jar. If you want to be sure you're using the correct plugin,
simply delete the other versions from your maven installation dir and
delete the .maven/plugins dir.
-Vincent
>
> I'll keep plugging away.
>
> Keith
>
> ps. Exception:
>
> Exception in thread "main" java.lang.NoSuchMethodError:
>
org.aspectj.runtime.reflect.Factory.makeSJP(Ljava/lang/String;Lorg/aspec
tj
> /lang/Signature;I)Lorg/aspectj/lang/JoinPoint$StaticPart;
> [cactus] at
>
org.apache.cactus.util.ClassLoaderUtils.<clinit>(ClassLoaderUtils.java)
>
> On Sat, 2004-01-17 at 00:06, Vincent Massol wrote:
> > > -----Original Message-----
> > > From: Keith Irwin [mailto:keith@keithirwin.com]
> > > Sent: 17 January 2004 01:14
> > > To: 'Cactus Users List'
> > > Subject: RE: cactus maven plugin and resources
> > >
> > > 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?
> >
> > Ok here are the steps to perform (not real easy for now as we
haven't
> > yet integrated the maven plugin properly in the overall build):
> >
> > - go in jakarta-cactus/framework and type "ant dist"
> > - go in jakarta-cactus/integration/ant and type "ant dist"
> > - copy and rename the generated 2 jars into your local Maven
repository
> > (in [repository]/cactus/jars. Name them cactus-13-1.6dev.jar and
> > cactus-ant-13-1.6dev.jar.
> > - go in jakarta-cactus/integration/maven and type "maven
plugin:install"
> >
> > You can now use the Maven plugin for Cactus.
> >
> > Thanks
> > -Vincent
> >
> > >
> > > Keith
> > >
> > > > -Vincent
> > > >
> > > > > -----Original Message-----
> > > > > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > > > > Sent: 16 January 2004 23:11
> > > > > To: 'Cactus Users List'
> > > > > Cc: keith@keithirwin.com
> > > > > 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: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
> > > > > 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:
> > cactus-user-unsubscribe@jakarta.apache.org
> > > > > > For additional commands, e-mail:
> > cactus-user-help@jakarta.apache.org
> > > > >
> > > >
> > > >
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
cactus-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail:
cactus-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
cactus-user-help@jakarta.apache.org
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
RE: cactus maven plugin and resources
Posted by Keith F Irwin <ke...@keithirwin.com>.
Vincent--
Re: log resources for cactus runs only...
I snagged the code out of CVS this morning, hunted down all the
dependencies, created build.properties, and produced the two jars, ran
the maven plugin install, copied the jars into the repository, and
removed all the other jars (just to see) and even changed my
project.xml.
Maven insists on downloading a 2003 version of the 1.6dev branch (maybe
for some other issue), but now I get an aspectj error. (See postscript
below.)
I do remember that when building, I got a "can't find aspectj.jar" even
though it seems to be on every path.
I'll see if I can track that down.
Meanwhile, how do I know if my project/maven is using the "new" plugin
jars? (I'd like to be able to report that it worked or didn't work
based on the right code. ;)
I'll keep plugging away.
Keith
ps. Exception:
Exception in thread "main" java.lang.NoSuchMethodError:
org.aspectj.runtime.reflect.Factory.makeSJP(Ljava/lang/String;Lorg/aspectj/lang/Signature;I)Lorg/aspectj/lang/JoinPoint$StaticPart;
[cactus] at
org.apache.cactus.util.ClassLoaderUtils.<clinit>(ClassLoaderUtils.java)
On Sat, 2004-01-17 at 00:06, Vincent Massol wrote:
> > -----Original Message-----
> > From: Keith Irwin [mailto:keith@keithirwin.com]
> > Sent: 17 January 2004 01:14
> > To: 'Cactus Users List'
> > Subject: RE: cactus maven plugin and resources
> >
> > 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?
>
> Ok here are the steps to perform (not real easy for now as we haven't
> yet integrated the maven plugin properly in the overall build):
>
> - go in jakarta-cactus/framework and type "ant dist"
> - go in jakarta-cactus/integration/ant and type "ant dist"
> - copy and rename the generated 2 jars into your local Maven repository
> (in [repository]/cactus/jars. Name them cactus-13-1.6dev.jar and
> cactus-ant-13-1.6dev.jar.
> - go in jakarta-cactus/integration/maven and type "maven plugin:install"
>
> You can now use the Maven plugin for Cactus.
>
> Thanks
> -Vincent
>
> >
> > Keith
> >
> > > -Vincent
> > >
> > > > -----Original Message-----
> > > > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > > > Sent: 16 January 2004 23:11
> > > > To: 'Cactus Users List'
> > > > Cc: keith@keithirwin.com
> > > > 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: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
> > > > 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:
> cactus-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail:
> cactus-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
RE: cactus maven plugin and resources
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Keith Irwin [mailto:keith@keithirwin.com]
> Sent: 17 January 2004 01:14
> To: 'Cactus Users List'
> Subject: RE: cactus maven plugin and resources
>
> 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?
Ok here are the steps to perform (not real easy for now as we haven't
yet integrated the maven plugin properly in the overall build):
- go in jakarta-cactus/framework and type "ant dist"
- go in jakarta-cactus/integration/ant and type "ant dist"
- copy and rename the generated 2 jars into your local Maven repository
(in [repository]/cactus/jars. Name them cactus-13-1.6dev.jar and
cactus-ant-13-1.6dev.jar.
- go in jakarta-cactus/integration/maven and type "maven plugin:install"
You can now use the Maven plugin for Cactus.
Thanks
-Vincent
>
> Keith
>
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > > Sent: 16 January 2004 23:11
> > > To: 'Cactus Users List'
> > > Cc: keith@keithirwin.com
> > > 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: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
> > > 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:
cactus-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail:
cactus-user-help@jakarta.apache.org
> > >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
RE: cactus maven plugin and resources
Posted by Keith Irwin <ke...@keithirwin.com>.
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:vmassol@pivolis.com]
> > Sent: 16 January 2004 23:11
> > To: 'Cactus Users List'
> > Cc: keith@keithirwin.com
> > 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: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
> > 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: cactus-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
RE: cactus maven plugin and resources
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Keith Irwin [mailto:keith@keithirwin.com]
> Sent: 17 January 2004 00:02
> To: Cactus Users List
> Subject: RE: cactus maven plugin and resources
>
> Vince--
>
> Okay, I'll have to figure out how to check it out of CVS, compile,
etc,
> etc and see what I can get going.
>
> Is the idea here that you the "client" should take care of the output
> when running "maven cactus" and the "server" is just stuff that shows
up
> in the app server output (or whatever you've configured)?
Client = JVM where the JUnit Test Runner executes
Server = container JVM
-Vincent
>
> If so, makes sense.
>
> Keith
>
> 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
> >
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > > Sent: 16 January 2004 23:11
> > > To: 'Cactus Users List'
> > > Cc: keith@keithirwin.com
> > > 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: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
> > > 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:
cactus-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail:
cactus-user-help@jakarta.apache.org
> > >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
RE: cactus maven plugin and resources
Posted by Keith Irwin <ke...@keithirwin.com>.
Vince--
Okay, I'll have to figure out how to check it out of CVS, compile, etc,
etc and see what I can get going.
Is the idea here that you the "client" should take care of the output
when running "maven cactus" and the "server" is just stuff that shows up
in the app server output (or whatever you've configured)?
If so, makes sense.
Keith
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
>
> -Vincent
>
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > Sent: 16 January 2004 23:11
> > To: 'Cactus Users List'
> > Cc: keith@keithirwin.com
> > 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: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
> > 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: cactus-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
RE: cactus maven plugin and resources
Posted by Vincent Massol <vm...@pivolis.com>.
*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
-Vincent
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: 16 January 2004 23:11
> To: 'Cactus Users List'
> Cc: keith@keithirwin.com
> 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: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
> 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: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
RE: cactus maven plugin and resources
Posted by Vincent Massol <vm...@pivolis.com>.
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: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
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: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org