maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Lampada (JIRA)" <>
Subject [jira] (MNG-5102) Mixin POM fragments
Date Tue, 02 Oct 2012 20:05:38 GMT


Tony Lampada commented on MNG-5102:

Now that maven-tiles has been successfully packed as an [open source project|],

I made a small project that demonstrates how, using maven-tiles, one can get the desired mixin

See attached [|]

Thanks Maurizio!
> Mixin POM fragments
> -------------------
>                 Key: MNG-5102
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Wish
>          Components: POM
>    Affects Versions: 2.2.1
>            Reporter: Anthony Whitford
>             Fix For: 3.1
>         Attachments:,
> 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
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message