Hi Manuel,
As you, I am really interesting to understand how to use the
src/main/config directory.
It would be nice to have an example that explains the differences
between src/main/resources and src/main/config and how to use them
in the maven build.
Any help would be great,
Thanks,
Rémy
2006/10/10, Manuel Ledesma <[EMAIL PROTECTED]>:
According to Betters Builds with Maven book
* src/main/resource : standard location for application resources
(images, etc, and properties files, which can be used for configuration
too).
* src/main/config : standard location for application configuration
files.
Src/main/config does look to involve in any of the lifecycle of maven, Can
someone explain me the difference?
I can see a use in my case, But I don't see how to apply the concept in
maven worlds. For example we could use resource to hold configurations,
which values do not change from environment-environment (eg: testing, User
Acceptance, Staging and Production) and use config to hold configuration
for
values that change from environment-environment like a database name, etc.
The problem I'm having is how I can produce such a jar or a procedure to
get
all configuration files coming from config directories, apply some
filters.
I can see probably various solutions for it:
1. Create a plugin, which will produce a jar following some standard,
like ${artifactId}-config-${version}, but the problem with this is that
maven only outputs and deploys a single file.
2. Create another plugin to push all configuration files under some
project directory and use a simple jar for it.
I like option 1, but I will need help or hints on how to produce
additional
jars and deploying too.
