You seem to be on the right track. One statement was a bit confusing:
On 25/02/2009, at 8:47 AM, John Wooten wrote:
Since each product uses different combinations of processors,
configurations, etc., do the product poms use the children modules,
and the children don't have
anything about their parents since they might be different? It's
clear that engine's pom has to have foundation pom as a dependency,
and so forth in some of
the others.
All the children should have parents consistent with the structure of
the layout. There should be a 1:1 relationship with the parent and the
modules. Consider your release patterns as well - you want to make
sure a releasable unit is buildable together from a common root.
Products should have dependencies on stuff from /modules in your case,
which I think you have correct.
Hope this helps.
- Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
