You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2014/12/14 13:44:13 UTC
[jira] [Resolved] (NIFI-167) Enhancement to support Maven 3.X
instead of Maven 3.2.X
[ https://issues.apache.org/jira/browse/NIFI-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt resolved NIFI-167.
------------------------------
Resolution: Fixed
Fix Version/s: 0.0.1
Assignee: Joseph Witt
Both patches provided have been applied. Tested a full clean build now working all the way back to 3.0.5 and a full clean build on Maven 3.2.3. So the patch appears to have successfully relaxed the maven requirement to 3.x.
Thank you very much for the contribution.
> Enhancement to support Maven 3.X instead of Maven 3.2.X
> -------------------------------------------------------
>
> Key: NIFI-167
> URL: https://issues.apache.org/jira/browse/NIFI-167
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 0.0.1
> Reporter: Karl Heinz Marbaise
> Assignee: Joseph Witt
> Priority: Minor
> Labels: maven, patch
> Fix For: 0.0.1
>
> Attachments: 0001-NIFI-167-Added-appropriate-Maven-configuration-to-bu.patch
>
>
> It looks like the nar-maven-plugin seemed to be the limiting factor in running Maven 3.2.X instead of Maven 3.X
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)