Wayne Fay wrote:
>
>> The source code must be common, dev1, dev2 etc. are different
>> environments
>> differs only in configuration files.
>
> In that case, I would probably use profiles (which were designed for
> this purpose exactly) and structure the project as follows:
> no dev1, dev2 directories
> common has all files including config in the proper directory
> (src/main/resources)
> create "dev1" and "dev2" profiles with various values that are
> filtered into the config files during the build, also the profiles
> would set classifiers "dev1" and "dev2" or whatnot
>
>
Hi Wayne,
my structure requires multiple levels as you see and because of lack of
profile
inheritance I cannot do it on that way.
Anyway I played with profiles and I like it, but unfortunately isn't useful
here.
Czollli
--
View this message in context:
http://www.nabble.com/Multimodule%2C-multilevel-project-tp21806770p21827230.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
