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

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132910#comment-13132910 ] 

Nick Boldt commented on JBIDE-17281:
------------------------------------

Since the one PR [1] on this topic is ancient (May 2014!) I'm inclined to close it and request that we instead either start a new one, or start moving individual requirements from plugins to pluginManagement one by one so it's easier to review & apply.

[1] https://github.com/jbosstools/jbosstools-build/pull/143

[~dgolovin] WDYT? 

> 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.4.x
>
>
> 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 reduce clutter in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml 
> - move update site manipulations to site/pom.xml 
> - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse
> - etc.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)