accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-2775) Plugin configurations for a module should be in build/plugins rather than pluginManagement
Date Tue, 06 May 2014 17:39:16 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Busbey updated ACCUMULO-2775:
----------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.5.2)
                       (was: 1.6.1)
                       (was: 1.7.0)
           Status: Resolved  (was: Patch Available)

Christopher prefers the future proofing offered by keeping things in the pluginManagement,
in the event that those modules later get sub-modules.

> Plugin configurations for a module should be in build/plugins rather than pluginManagement
> ------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2775
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2775
>             Project: Accumulo
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>              Labels: maven
>
> Several modules (that do not themselves have submodules) define plugin configurations
in pluginManagement rather than plain plugin sections.
> So long as no plugins or pluginManagement sections in parent poms define configurations,
this works fine.
> However if you e.g. have a "patches" directory in your top build area and wish to tell
rat to ignore it, all of the module-level rat exclusions will suddenly fail.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message