i have a multi-module project that looks like this:
-- parent
|-- profiles.xml
|-- pom.xml
|-- childProjectJar
|--profiles.xml
|--pom.xml
|-- childProjectEjb
|-- profiles.xml
|-- pom.xml
one profile is defined in parent/profiles.xml, and environment specific
(dev, test, uat) profiles are defined in childProjectJar/profiles.xml and
childProjectEjb/profiles.xml. when i run mvn install from ./parent,
childProjectEjb fails because i reference a property defined by a profile in
./parent/profiles.xml. however, when i build from childProjectEjb, it picks
up that profile's value without problem and builds cleanly.
am i using profile inheritance incorrectly? is there a better way to do
this?
--
View this message in context:
http://www.nabble.com/profile-inheritance-problem-tf1961199.html#a5380353
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
