Is there a reason that you need this?
The test and jar plugins both use:
maven java:jar-resources
To do this, with more customization that either of the two solutions
provide. It does this:
<j:if test="${maven.has.jar.resource.patterns}">
<!-- Copy any resources that must be present in the deployed
JAR file.
-->
<copy todir="${maven.build.dest}">
<fileset dir="${maven.jarResources.basedir}">
<patternset refid="maven.jar.resources.set"/>
</fileset>
</copy>
</j:if>
So, if you specify jar resources in your project.xml, it should happen
automatically...?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
Ben Walding <[EMAIL PROTECTED]> wrote on 11/09/2002 05:45:17 PM:
> My preference is to go one further...
>
> <copy todir="${maven.build.dest}">
> <fileset dir="${maven.src.dir}" excludes="**/*.java"/>
> </copy>
>
>
>
> David Garnier wrote:
>
> >Hello,
> >While developing my Struts-based webapp, I hit the following problem in
> >the maven-java plugin: .properties files in the src/ dir doesn't follow
> >the classes when they are compiled. There is a simple fix, add theses
> >lines at the end of the java:compile goal :
> >
> > <copy todir="${maven.build.dest}">
> > <fileset dir="${maven.src.dir}" includes="**/*.properties"/>
> > </copy>
> >
> >Best Regards,
> >David Garnier
> >
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
