[
https://issues.apache.org/jira/browse/NIFI-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514515#comment-14514515
]
ASF subversion and git services commented on NIFI-271:
------------------------------------------------------
Commit 9a3b6bed62e9962ff97f2c76055cd4d49705ff89 in incubator-nifi's branch
refs/heads/develop from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=9a3b6be ]
NIFI-271
> 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)
