On Thu, 2003-09-11 at 13:49, Rafal Krzewski wrote: > Norbert Pabiś wrote: > > > Yes. > > You said you don't want users to have 20 dependencies in project.xml. > > I do not want to have any. If there will default project.xml with > > preferred versions > > with a possibility to change it - that sounds good to me. > > Sounds interesting, but it's rather hard to achieve. First it would > require multi-level POM inheritance. At the momen Maven supports only > sinle level of inheritance.
Not so in some newer code. I want to release 1.x so I can expose some new stuff :-) > Second it would require intelligent merging > of dependencies: at this moment declaring any dependencies in the child > project discards all inforamtion about parent project's dependencies. Not true. Right now they are aggregated, there is an exception made for dependencies. > I believe that Maven will support both of these things in the future > (post 1.0, definetely). When they are in place you could have: > > defaluts.xml (distributed with maven, contains deps on known good > | plugins at the time of the release) > | > V > common.xml (settings for the whole project) > | > | > V > project.xml (settings for a particular module) Yes, things will be much further with components. I promise :-) > R. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- 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]
