[jbosstools-issues] [JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

[Mickael Istria (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Istria updated JBIDE-17281:
-----------------------------------

    Fix Version/s: LATER
                       (was: 4.2.0.Beta2)
         Assignee: Denis Golovin  (was: Mickael Istria)


Moving it to LATER and re-assigning to Denis as I don't see any reason why this change improves anything, at the contrary, it would make maintenance more difficult.

[~dgolovin]: Can you please elaborate on what this does resolve? The parent/pom.xml is where we factorize things that we want all modules to have. Jacoco is a good example: we prefer having it in parent pom rather than having it once in every component. Same thing for site manipulation.

> parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
> ------------------------------------------------------------------------------------
>
>                 Key: JBIDE-17281
>                 URL: https://issues.jboss.org/browse/JBIDE-17281
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>            Priority: Optional
>             Fix For: LATER
>
>
> The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins.  It would let to do further clean up and dcluttering in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml
> - move update site manipulations to site/pom.xml 
> - etc



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)