Jorg,
Thanks for the reply.
Thanks for the tip on help:activeprofiles - it shows dev - so maybe I have
a different problem.
I created a simple set of projects using archetype:generate - a parent
project and a child project for a multimodule project, parent builds child.
I ran some tests with
Hi,
activeByDefault always meant that this profile is only active if none other
is. If you e.g. have added a profile for M3's site plugin to use the POM for
M2 or M3, well, then you have now an active one ;-)
This is sorry to say simply wrong, cause if that would be true using
activeByDefault
Hi,
to activate your dev-profile you need to it a little bit tricky...
You need to define in the settings.xml a thing like the following:
profile
idtest-dev/id
activation
activeByDefaultfalse/activeByDefault
/activation
properties
Hi All,
I am currently upgrading to maven 3 from 2. I have a settings.xml that I
have been using for a couple of years now. It has a profile in it called
dev it looks something like this:
profiles
profile
iddev/id
Hi Todd,
tpatch wrote:
Hi All,
I am currently upgrading to maven 3 from 2. I have a settings.xml that I
have been using for a couple of years now. It has a profile in it called
dev it looks something like this:
profiles
profile
iddev/id
activation
