Am 05.12.2016 um 15:31 schrieb Chas Honton: > What problems are you trying to solve with mixins? What is missing from the > current inheritance scheme? > > It appears to me that you are putting the "how before the "what". > > My personal experience is that mixins lead to jar hell rather fast.
In my understanding, there are no jar files involved. It's just a more flexible way to compose an effective model and allows far more re-use. The "what" becomes a matter of what user's are going to do with those possibilities. The mixins are not about aggregating projects to build in one go, as I understand it. They are about composition of an effective model. As has already been said in this thread, maybe the parent/child hierarchy is not needed anymore - aggregation can be expressed in other ways more easily (a <projects> element instead of <modules>, for example. Maybe in a way decoupling from any kind of directory layout. Where we have <module>some-directory</module> today, we may have <project scmUrl=""/> in POM 5. By this I mean the first build will checkout the project for you automatically. You only need the "master" POM and the first invocation of "mvn" will checkout the aggregator automatically in some way. Just thoughts, though.) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
