Sure, that is along the lines of what I'm proposing, but instead of a
pre-callback, we can just add that directory directly into the classpath for
the unit test run.  src/test-conf works for me.

=================================================================
Jeffrey D. Brekke                                   Quad/Graphics
[EMAIL PROTECTED]                              http://www.qg.com


> -----Original Message-----
> From: James Taylor [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 31, 2002 6:58 AM
> To: 'Turbine Maven Developers List'
> Subject: RE: [PROPOSAL] Including resources in compile paths (main jar
> and tests)
> 
> 
> In JCS I'm using src/test-conf which gets copied to 
> target/test-classes
> by a pre-test callback. I like that better than src/test/conf 
> because I
> like the idea of having the src directories at the same 
> directory level
> (since they both end up at the root of the classpath). Does that even
> make sense?
> 
> On Fri, 2002-05-31 at 07:50, Brekke, Jeff wrote:
> > I was thinking more of a directory under src/test, something like
> > src/test/conf.
> > If you copy config files for testing, where would you copy 
> them from?  
> > I've always used two config files, one for production and 
> the other for
> > testing.
> > 
> > =================================================================
> > Jeffrey D. Brekke                                   Quad/Graphics
> > [EMAIL PROTECTED]                              http://www.qg.com
> > 
> > 
> > > -----Original Message-----
> > > From: Vincent Massol [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, May 31, 2002 3:34 AM
> > > To: 'Turbine Maven Developers List'
> > > Subject: RE: [PROPOSAL] Including resources in compile 
> paths (main jar
> > > and tests)
> > > 
> > > 
> > > Hi Jeff,
> > > 
> > > > -----Original Message-----
> > > > From: Brekke, Jeff [mailto:[EMAIL PROTECTED]]
> > > > Sent: 31 May 2002 02:29
> > > > To: 'Turbine Maven Developers List'
> > > > Subject: RE: [PROPOSAL] Including resources in compile 
> > > paths (main jar
> > > and
> > > > tests)
> > > > 
> > > > For the unit tests I thought about just providing a 
> > > directory that we
> > > > could include in the testing classpath.  Would this be 
> > > enough?  If we
> > > have
> > > > a
> > > > different directory for the testing properties, would 
> we need the
> > > > <resourceTestPatters/> stuff?
> > > > 
> > > 
> > > That would do it but you would usually mean having your src/test
> > > directory in the classpath, which I don't think is a nice 
> practice at
> > > all. I'd much much rather have a way to copy test resources 
> > > to the test
> > > classes/ directory.
> 
> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to