> > Now, if project B's pom is stored in the local repo with no 
> properties
> > resolved (i.e. the pom file is not the interpolated 
> version) then project 
> > A needs to have definitions for these properties. This would not be 
> > possible unless the properties files are also made 
> available in the local 
> > repo, or if the repo version of the pom had been interpolated.
> 
> I honestly haven't seen many <dependencies/> elements that 
> require property interpolation. Do you have cases that 
> require interpolation within the dependencies?
> 
> > Also, if project B's pom states that it extends (for example)
> > ${basedir}/../../project.xml, how does project A get access 
> to the correct 
> > parent definition?
> 
> This was overcome in the plexus component builds by actually 
> extending POMs located in the local repository. So as part of 
> your build process you install the necessary POMs before any 
> child considerations. This was in fact done to deal with the 
> scenerio you outline above.

Can you (briefly) explain how this works?  I'm not thoroughly aware of
Plexus and I even browsed the source code from ViewCVS from the link you
provided below and I'm not sure where to look because there is a ton of code
in the codehaus Plexus project.
 
> > The only solution I can see is for installed poms to be fully 
> > interpolated
> > and extended to include the parent info before being 
> serialised to the 
> > repo. I get the feeling that I'm missing something here, 
> I'd appreciate it 
> > if you could try to fill in the gaps. :)
> 
> I think extension from the local repository solves this 
> problem, but I would still like to know if you are using 
> interpolation within the dependnecy elements themselves as 
> that is something I would like to formally limit if possible.
> 
> > I'd be more than happy to take on some of the effort - just 
> drop me a 
> > line
> > with the details.
> 
> You might want to take a quick peek at the plexus build which 
> works with POMs installed in the local repository and see if 
> the use case you have in mind would work with the assumptions 
> with the plexus component build and then we can go from 
> there. I'm also always in IRC on irc.codehaus.org#maven if 
> you want to chat.
> 
> The plexus stuff is here:
> 
http://cvs.codehaus.org/viewcvs.cgi/plexus/?root=codehaus

> Cheers,
> Mike
> 
> __________________________
> Mike Melia
> ThoughtWorks Inc.
> http://www.thoughtworks.com
> mobile: +61 0421 581 959
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational and technical
order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
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]

Reply via email to