[
https://jira.codehaus.org/browse/MNG-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282705#comment-282705
]
Darren Hartford commented on MNG-5102:
--------------------------------------
Just to make sure there is an appropriate discussion on other points-of-view:
as a consumer of different maven plugins/other projects there are times when
each individual plugin/project requires a large amount of configuration within
the pom (particularly third-party plugins). If mixin is intended to help
mitigate this problem, great, just didn't want to assume without asking :-)
Examples include the maven-gwt-plugin which requires a good amount of
configuration, as well as Enunciate. Having those plugins be able to provide
example mixin file that only focuses on their particular plugin will avoid a
lot of merging problems that usually occur in sometimes very large pom.xml
files.
> Mixin POM fragments
> -------------------
>
> Key: MNG-5102
> URL: https://jira.codehaus.org/browse/MNG-5102
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: POM
> Affects Versions: 2.2.1
> Reporter: Anthony Whitford
> Fix For: 3.1
>
> Attachments: maven-tiles.zip
>
>
> I am looking for a way to _mixin_ POM fragments into POMs. Note that this
> idea is beyond parent pom inheritance because all projects inherit from a
> corporate parent pom. The problem that I am running into is that the
> corporate parent pom is turning into an _"everything but the kitchen sink"_
> POM and I'd like to dissect it into POM fragments relevant for individual
> modules.
> For example, I would like to have mixins for:
> * Java projects (that include static code analysis plugins, javadoc, etc.)
> * JPA projects (that include DDL generation)
> * Flex projects (that include flexmojos, asdoc, etc.)
> * Scala projects (that include the maven-scala-compiler plugin, scaladoc,
> etc.)
> * JavaScript projects (that include build plugins like
> maven-yuicompressor-plugin with jslint and compress goals)
> Hopefully, you get the idea. Without the ability to factor pom logic, we are
> left with two symptoms:
> # copy/paste duplication
> # complex _"it does it all"_ parent poms (which slow down builds because more
> plugins are loaded even though they might not do anything material)
> Note that a project may include multiple mixins as I could have a project
> that contains Java code, Scala code, and JavaScript.
> Another idea is that the mixins could be parameterized, so that the ultimate
> pom can be customized based on the parameters (like tokens).
> I recall reading about Mixins coming in Maven 3.1, but could not find any
> such issue to watch, so am creating one.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
