My team never found a solution. After thinking it over I believe that this was by design in that Maven was not meant to be used in this way. In the future, we will create separate project hierarchies and use a shared local repository for integration.
jtdeane wrote: > > I have defined a profile within my settings.xml file (located in > maven/config) and activated it. I then utilized those profile properties > throughout a multi-project hierarchy. Everything resolves and builds if I > execute an mvn install from the hierarchies top level POM. However, if I > go into a lower level POM.xml and execute those commands the properties do > not resolve. > > My understanding is that profiles defined within settings.xml are global > so is this a defect? Or is there something I am missing?? Any ideas or > solutions would be truly appreciated. Thank you! > > -- View this message in context: http://www.nabble.com/Profile-Properties-Defined-In-Settings.xml-Within-Multi-Project-Environment-tf3178303s177.html#a9312002 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
