Good observation, but that's not it. I had to edit the profile.xml pasted
here to make it easier to follow.
Besides, 'mvn validate' would have caught that. Any other ideas?
--
View this message in context:
Hi Danny.
I can guess that what you're missing is
profile
idprof1/id
activation
activeByDefaultfalse/activeByDefault
/activation
properties
.
.
.
/profile
So, it's up to you to specify from command line for example, the active
profile
Yes, I thought about that last night, but according to the Maven 2 schema,
'false' is the default value for 'activeByDefault'.
But then again, you might be on to something, since Maven apparently thinks
that all three profiles are active (according to 'mvn
help:active-profiles'), which seems to
Carlos,
the profiles are indeed active by default, which contradicts the Maven POM
schema(!) Perhaps there's another schema that applies to external profiles
such as in my case since I was using profiles.xml (or I'm not interpreting
the schema correctly). Oh well, it doesn't really matter now.
Hi!
It seems that the profile activation isn't working for me, even though I
explicitly tell Maven to activate it with the -P option.
Background:
I have an external profile file (profiles.xml) that has some properties in
each profile section:
profiles
profile
idprof1/id
properties
distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
Date: Tue, 2 Sep 2008 12:51:30 -0700
From: [EMAIL PROTECTED]
To: users@maven.apache.org
Subject: Explicit Profile Activation doesn't work for me
Hi
