Thanks for your reply. The point is having a handful of properties,
managing them inside an xml file making it really long and difficult.
Can't we simply load a property file for each profile and define the
properties there?
hi arash,
as far as i am aware (i've only been using maven for about 6 m
hi arash,
as far as i am aware (i've only been using maven for about 6 months so
i'm no real authority on it) but the easiest way to accomplish is to
have the properties defined in the environment profiles, eg in your main
pom:
build
env
build
Put the properties themselves inside the profiles. Or, use filtering
with various named filters eg qa.filter and specify the proper filter
to use in your profile.
Wayne
On 2/1/08, Arash Bizhan zadeh <[EMAIL PROTECTED]> wrote:
> Hi all,
> I know it is a well known issue but I am really stuck!
> I
Hi all,
I know it is a well known issue but I am really stuck!
I am in the process of migrating some Java applications build system to
Maven 2. developers need to build the applications for different environment
like local/staging/QA/prod. in the old build system we have one property
file including
