On Sun, Dec 12, 2010 at 10:45 AM, Benson Margulies <[email protected]> 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?
Have you considered the case where someone only has a single module of your build checked out? In that case globalRoot will be pointing to something that does not exist. The way you are trying to solve the problem doesn't feel right. Can you explain what you are trying to do? I vaguely remember someone else talking about large resource sets and exploding them inside your ~/.m2/repository. I'm not sure this is similar to your problem, but we do Eclipse RCP development and use maven-dependency-plugin:unpack to extract the eclipse RCP (+delta packs) where we have manually added the zips to our internal repository. So as long as we don't "clean" that project out, we have the large target platform exploded for use by the development team. But this isn't referenceable by other maven modules. There may be some guidance on the war/ear plugin since merging this stuff may be relevant there. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
