[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:comment-tabpanel&focusedCommentId=12969967#comment-12969967 ] 

Mickael Istria commented on JBIDE-17281:
----------------------------------------

[~dgolovin]: I really believe that's not worth the effort, although it's indeed semantically cleaner.
The only drawback of factorizing the plugin executions in parent pom is that it will startup a few not relevant mojos on some modules. But those mojos have a very low cost in term of time, so the gain is just a some lines saved in the build log.
If you go for that change, it will take you much time to adapt all components, and there are risks of forgetting some. So I think the effort/risk is very high compared to the benefits.

> 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: 4.2.0.Beta3
>
>
> 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)