Today I found a workaround which is somehow not optional but keeps me alive.
All the base artifact types of a certain platform type will be put into a super-pom for that platform type. E.g. jee-super-pom. Each artifact base type plugin and properties is encapsulated into a Profile. The profile is activated by a file that exists in the child project. Now the aggregator project myapp-pom can inherit from the jee-super.pom. Each module module-pom will have a file e.g. javalib-architype, groovylib-architype, basemodel-architype, testimpl-architype. This will activate the base architype profiles. Drawback is that this leaves the module-pom projects with funny empty marker files in the project folder and the files cannot be looked up in the repository as they are no architypes. What I find rather annoying is that even the activiation condition based on properties will not work as the parent profiles will only be triggered by parent properties and not by properties defined in the module-pom. So I just hope someday or earlier then later someone will add a feature to Maven to resolved the parent properties, then the child properties and then start resolving the profiles only. Or let us keep the hope up some one delivers the MIXIN feature. /Richard -----Original Message----- From: ext Wayne Fay [mailto:[email protected]] Sent: Wednesday, April 13, 2011 8:19 PM To: Maven Users List Subject: Re: Expected implementation date for Maven MIXIN Feature > AM gets the version from A through the parent relationship. > AM gets the plugin sce.model from the MIXIN relationship to M. > > AI gets the version from A through the parent relationship. > AI gets the plugin sce.compile from the MIXIN relationship to I. Sounds roughly like composition of objects/projects in the POM, is that about right? I haven't really been following any discussion of Mixins previously. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
