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.

-Vincent

> http://www.mail-archive.com/turbine-maven-
> [EMAIL PROTECTED]/msg00584.ht
> ml
> 
> =================================================================
> Jeffrey D. Brekke                                   Quad/Graphics
> [EMAIL PROTECTED]                              http://www.qg.com
> 
> 
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 5:30 PM
> > To: Turbine Maven Developers List
> > Subject: Re: [PROPOSAL] Including resources in compile paths (main
jar
> > and tests)
> >
> >
> > On Thu, 2002-05-30 at 17:06, Vincent Massol wrote:
> > > Hi,
> > >
> > > I have a problem with one problem I am mavenizing. It needs some
> > > resources (properties and xml files) put in its generated
> > jar. Also, the
> > > junit test cases expect some resources files (xml,
> > properties, etc) to
> > > be in the test class directories.
> > >
> > > I have had a look at jarResources but it seems to be for a
> > different use
> > > (it simply copies resource file to the jar and not to the
generated
> > > class directory).
> > >
> > > I think this is a very common case ... Actually, so common,
> > that I may
> > > be missing something. Am I ?
> > >
> > > I would like to propose either :
> > >
> > > 1/ the addition to some (optional) elements in the POM, as in :
> > >
> > >     <resourcePatterns>
> > >       <resourcePattern>include = **/*.properties</resourcePattern>
> > >
> > >       <resourcePattern>include = **/*.xml</resourcePattern>
> > >     </resourcePatterns>
> > >
> > >     <resourceTestPatterns>
> > >       <resourceTestPattern>include =
> > > **/*.properties</resourceTestPattern>
> > >       <resourceTestPattern>include =
**/*.xml</resourceTestPattern>
> > >     </resourceTestPatterns>
> > >
> > > (in the same spirit as <unitTestPatterns>)
> >
> > +1
> >
> > The crappy jarResources handling is my bad. The resources should
have
> > been copied into the classes/ directory, or at the option should
have
> > been provided to if so desired. This will be nice.
> >
> > > or
> > >
> > > 2/ the addition of some Ant properties, as in :
> > >
> > > maven.compile.resourcePatterns = **/*.properties,**/*.xml
> > > maven.compile.resourceTestPatterns = **/*.properties,**/*.xml
> > >
> > > My preference goes to 1/. Please tell me what you prefer
> > and I'll submit
> > > a patch.
> > >
> > > Thanks
> > > -Vincent
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > --
> > jvz.
> >
> > Jason van Zyl
> > [EMAIL PROTECTED]
> >
> > http://tambora.zenplex.org
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
> 
> --
> To unsubscribe, e-mail:   <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>



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

Reply via email to