On Fri, 2003-12-26 at 13:48, David Zeleznik wrote:I have to wonder whether inheritance is really a better way to go over composition of the project definition. OOP went down the path of inheritance for a long time, but it is now generally recognised that you can get yourself into a horrible horrible mess with deep inheritance hierarchies. Witness component driven design which typically uses composition to acquire behaviour. I am not suggesting that having project "fragments" would be a good idea, just that it might be an idea.
Hi,
I am about to submit a bug report on Jira, but I wanted to post details to
the list first. We make extensive use of the PomTag (ie. m:pom) in our jelly
scripts and plugins to be able to share dependencies and other project
properties beyond the single inheritance of <extends>.
Just out of curiosity how many levels of inheritance do you use? You probably don't watch the commits but in the maven-project component I have arbitrary levels of inheritance working. This component will be used be integrated in Maven soon.
Just a thought for the new year.
Ben
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
