maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MPOM-49) configure standard plugin-tools goals in parent pom
Date Sun, 17 Apr 2016 07:34:25 GMT

    [ https://issues.apache.org/jira/browse/MPOM-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244565#comment-15244565
] 

Michael Osipov commented on MPOM-49:
------------------------------------

Updated plugins will pickup this parent, old won't change. As far as I can see, Maven 2.x
is gone, profile isn't necessary, MPLUGIN-238 has been resolved. We just need to clarify the
override of {{default-descriptor}} to another phase.

> configure standard plugin-tools goals in parent pom
> ---------------------------------------------------
>
>                 Key: MPOM-49
>                 URL: https://issues.apache.org/jira/browse/MPOM-49
>             Project: Maven POMs
>          Issue Type: Improvement
>          Components: maven-plugins
>    Affects Versions: MAVEN-PLUGINS-25
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>             Fix For: MAVEN-PLUGINS-26
>
>
> actually, plugin descriptor creation, annotations dependency... are copy/pasted to every
plugin pom.xml even if they are the same
> creating a profile in parent based on site-pom.xml file inexistence (to avoid activation
during parent pom build) would permit to configure everything common in parent pom



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message