We use this a lot. All our projects are really subapplications
packaged up into jars, works greate except you can't jar up the
propoerties. We then just have one project to pull all the jars and
properties into a turbine application which is our portal.
We just added the following to the POM in the
<build></build> section:
<resources>
<resource>
<directory>${basedir}/src/templates</directory>
</resource>
</resources>
You can probably have includes/excludes in there also and of course
you would want to change the path to your location.
>>>>> On Wed, 5 Mar 2003 20:00:37 -0600 (CST), Will Holcomb <[EMAIL PROTECTED]> said:
> I have some webapp bits that I would like to use in other
> projects. What I am looking for is some way to have them packaged
> and accessed from a jar so that they are as easy as possible to
> distribute and update.
> I noticed with flux that if the screens, layouts, etc. directories
> are in the root of a jar on the classpath then they are accessible
> to the application. I am using maven however and my templates are
> buried down in the directory tree. When I put the path to them in
> the jar as a search path for templates in the Turbine.props they
> aren't found. (If they are in the root of the jar they are found.)
> I was just wondering if anyone had any suggestions that would let me
> stick with a pure maven build.
> Will
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
