> What happens if you move the activation part also to the
> parent? Hint: Maven
> cannot activate a profile from child to parent since the
> profiles in the
> parent have already be processed when the child is
> "interpreted". However,
> it is not clear to me if ${basedir} used in the parent is
> relative to the
> parent's physical location or to the one of the child.
Ok, so as I described, we have the master POM, then as a child we have the
project POM and then every module of course has its POM.
The problem is that the activation of the profile is in the master POM already,
since I don't want to reconfigure it several times.
So the only place to activate it would be the project POM, but as you write,
it's not possible to do that.
I don't think it's possible to configure a profile in some POM and then
reference it (for instance for activation) in a child POM. But I could be
wrong... :-)
As for ${basedir}, according to some discussions I read in the mailing list
archive, Maven properties are not resolved in profiles.
>
> > Also, to be sure, I added help:active-profiles, but this
> doesn't seem to
> > work in this case. For the successful build, it only lists
> the profile
> > which is active by default
> >
> > [INFO] [help:active-profiles]
> > [INFO]
> > Active Profiles for Project 'ch.ipi:util-di:jar:1.0.0-SNAPSHOT':
> >
> > The following profiles are active:
> >
> > - local (source: settings.xml)
> > - local (source: settings.xml)
> >
> > (and God only knows why it's listed twice...)
>
> Don't use "activeByDefault". Set it explicitly active in an
> activeProfiles
> section. Hint: Normally a profile activated by default should
> be not active
> if a different one is activated. However, it is not clear
> what "another one
> is activated" really means: another one is activated by
> command line or is
> activated by condition. Even worse that different maven
> versions do behave
> differently in this respect ;-)
Thanks, I'm going to try this one of these days.
Best regards,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
