nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-271) factor out a released common parent pom
Date Tue, 28 Apr 2015 04:14:06 GMT

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

Joseph Witt commented on NIFI-271:
----------------------------------

Getting feedback from aldrin piri, matt gilman, and mark payne that RAT is causing builds
to be quite long now.  Moving it back to a profile for activation.  It is something that must
be done as part of the release process and we can document it as a contribution/review step
as well.

> factor out a released common parent pom
> ---------------------------------------
>
>                 Key: NIFI-271
>                 URL: https://issues.apache.org/jira/browse/NIFI-271
>             Project: Apache NiFi
>          Issue Type: Task
>            Reporter: Benson Margulies
>            Assignee: Joseph Witt
>             Fix For: 0.1.0
>
>         Attachments: 0001-NIFI-271.patch, 0001-NIFI-271.patch, NIFI-271-Excluding-Eclipse-Project-Files-from-Rat.patch
>
>
> Arguably, there are a number of pieces of configuration and taste that are in common
between the 'nifi' and the 'maven-plugins' tree. If we wanted to apply DRY to this, we would
add a 'parent' directory, put a pom in there, and release _that_ first. 
> Or, on the other hand, we might feel that this is overkill. I don't think it's a good
idea to go here for 0.0.1 of anything, so I'm just writing this for future digestion.
> This parent pom should enforce certain conventions/formatting/etc.  to help make merging/diffs/reviews
easier.



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

Mime
View raw message