On 6/10/06, Max Cooper <[EMAIL PROTECTED]> wrote:
wolverine my wrote:
> The src/main/resources directory contains only the configurations
> which will be loaded by the classloader? So we really need to study
> the 3rd party library configurations to see if they are loaded via the
> classloader...
Do you want the files to end up in WEB-INF/classes (i.e. loaded from
classpath) or just WEB-INF (or some other directory, relative to webapp
root)? Maven doesn't really complicate things much here, since you have
to make those choices anyway. You don't need to look at the source code
of the component that does the loading in most cases.
>
> What should the src/main/config contains?
>
Nothing that I am aware of.
> Typicaly we have the scripts to start application or server, and
> scripts for utilities (backup, housekeeping), and what do you think if
> we save these scripts in /src/main/bin directory? Or do we save these
> scripts into difference directories?
src/main/bin sounds reasonable. You'll probably need to (eventually)
consider how you want these files to end up in a build artifact, and
then how you are going to tell maven to find them.
You can also create 2 modules, one for your webapp, one for your whole
distribution, and move all resources non required to create/test your
webapp into the distribution package, e.g. under src/main/resources.
I usually have something like
src/main/resources/bin
src/main/resources/conf
src/main/resources/lib
etc...
and use the assembly plugin to bundle everything together.
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
