I think the best thing is to create a test project that re-produces this.
Then create a jira and attach the test project. Explain the exact command
you execute, the actual outcome and what you expected the outcome to be.
Then it will be easy for someone to spot if it's a Maven issue or incorrect
That is not correct,
if I have a project structure like this:
A
|pom.xml
--- B
| pom.xml
And I define the profile profile1 in A/pom.xml when running :
B myuser$ mvn help:active-profiles -Pprofile1
[INFO] Scanning for projects...
[INFO] Searching repository for plugin
But try it with a profiles.xml file; for example, if I create a project with
the app-fuse archetype:
mvn \
archetype:create \
-DarchetypeGroupId=org.appfuse.archetypes \
-DarchetypeArtifactId=appfuse-modular-spring \
-DremoteRepositories=http://static.appfuse.org/releases \
hallo
glad to help :)
i have no mixture of the profiles neeeded for the builds within
settings.xml (so everyone who gets the pom can built it). you dont have
a profiles.xml too?
i have put everything in pom.xml profiles:
profiles
profile
idlocal/id
hallo
the profiles are not inherited to child modules, but the effects are. so
the child will not show the profile as active but it will work nontheless.
see: http://www.nabble.com/Profile-inheritance-tf2953156s177.html#a8259757
for a better explanation
regards
ossi
Philippe Le Marchand
Hi ossi, thank you very much for your reaction, I just figured it out
searching in Nabble's archives, so I prepared myself to ask for help
on what I needed instead of how to inherit profiles to accomplish it
:-)
So the idea is to:
- access the filter properties file corresponding to the target
Profiles are not inherited, period.
Now, having said that, profiles in parent POMs can be triggered by the
building of a child. When activated, they are applied directly to the parent
POM, prior to that parent being used for inheritance into the child. So, the
effects of an active profile in a
David Jackman [EMAIL PROTECTED] writes:
Are profiles inherited from parent poms? The scant (and confusing) docs
seem to imply that they are, but doing a help:active-profiles command
does not agree with this.
Please someone explain how this is supposed to work.
Hello,
As a follow-up
On 8/14/06, Douglas Ferguson [EMAIL PROTECTED] wrote:
Are profiles inherited from the parent pom?
They are supposed to be, although there have been a few issues here and
there. The one that bit us (Shale project) was MNG-2221[1], which looks
like it's been fixed for 2.0.5 when that is
Actually, profiles themselves are NOT inherited as such. Instead, they are
triggered when the parent POM delcaring them is loaded, and applied to that
parent POM. Then, the effects of the profile are inherited via normal parent
inheritance calculation.
It's a small difference in most cases, but
-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Monday, August 14, 2006 3:20 PM
To: Maven Users List
Subject: Re: Profile Inheritance
Actually, profiles themselves are NOT inherited as such. Instead, they are
triggered when the parent POM delcaring them is loaded, and applied to that
parent
PROTECTED]
Sent: Monday, August 14, 2006 3:20 PM
To: Maven Users List
Subject: Re: Profile Inheritance
Actually, profiles themselves are NOT inherited as such. Instead, they are
triggered when the parent POM delcaring them is loaded, and applied to
that
parent POM. Then, the effects of the profile
will profile1 activate for the
loading of pom a?
When I run mvn -Pprofile1 help:active-profiles it doesn't show.
D-
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Monday, August 14, 2006 4:25 PM
To: Maven Users List
Subject: Re: Profile Inheritance
right. if you ran
13 matches
Mail list logo
