You're probably better using the available plugin expressions for the execution root rather than this.
Also, the users@ list is the right place to ask the original question :) Cheers, Brett On 12/12/2010, at 11:15 AM, Benson Margulies wrote: > On Sat, Dec 11, 2010 at 7:05 PM, Benjamin Bentmann > <[email protected]> wrote: >> Benson Margulies wrote: >> >>> Say that, in a parent pom, there is an execution of a plugin that sets >>> a property. (e.g. the build helper plugin's port reserver). >>> >>> Will those properties inherit down to the children? >> >> No, the runtime data of project instances is separated. > > Let me explain what I had in mind, perhaps there's a better way to > accomplish it. > > I was about to walk over a hierarchy of about 20 poms adding, to each, > a property like: > > <globalRoot>../../..</globalRoot> > > where the number of ..'s would be different depending on the hierarchy > location of the POM. So, I had this inspiration: make a plugin that > could be stuck at the very top that would set a property to the > absolute path of the top, and let it trickle down. Then individual > projects could reference some large, slow-to-copy items up there with > ${globalRoot}/refrigerator. > > Of course, my plugin doesn't work due to what you just told me. So, I > wonder -- is there some other way to do this? > > > > >> >> >> Benjamin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
