Return-Path: 
 <commits-return-1790-apmail-nifi-commits-archive=nifi.apache.org@nifi.incubator.apache.org>
X-Original-To: apmail-nifi-commits-archive@minotaur.apache.org
Delivered-To: apmail-nifi-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4EC7810DBB
	for <apmail-nifi-commits-archive@minotaur.apache.org>;
 Sat,  3 Jan 2015 06:05:55 +0000 (UTC)
Received: (qmail 69155 invoked by uid 500); 3 Jan 2015 06:05:56 -0000
Delivered-To: apmail-nifi-commits-archive@nifi.apache.org
Received: (qmail 69113 invoked by uid 500); 3 Jan 2015 06:05:56 -0000
Mailing-List: contact commits-help@nifi.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@nifi.incubator.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@nifi.incubator.apache.org>
List-Post: <mailto:commits@nifi.incubator.apache.org>
List-Id: <commits.nifi.incubator.apache.org>
Reply-To: dev@nifi.incubator.apache.org
Delivered-To: mailing list commits@nifi.incubator.apache.org
Received: (qmail 69104 invoked by uid 99); 3 Jan 2015 06:05:56 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jan 2015 06:05:56 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Sat, 03 Jan 2015 06:05:54 +0000
Received: (qmail 68934 invoked by uid 99); 3 Jan 2015 06:05:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jan 2015 06:05:34 +0000
Date: Sat, 3 Jan 2015 06:05:34 +0000 (UTC)
From: "Joseph Witt (JIRA)" <jira@apache.org>
To: commits@nifi.incubator.apache.org
Message-ID: <JIRA.12764687.1420263611000.2678.1420265134414@Atlassian.JIRA>
In-Reply-To: <JIRA.12764687.1420263611000@Atlassian.JIRA>
References: <JIRA.12764687.1420263611000@Atlassian.JIRA>
 <JIRA.12764687.1420263611504@arcas>
Subject: [jira] [Updated] (NIFI-222) Versions of extensions should have no
 impact on ability to pull in artifacts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Joseph Witt updated NIFI-222:
-----------------------------
    Attachment: donothing-bundle.tar.gz

this is a bundle that uses a different version scheme from the rest of nifi.  It was used to prove the build was broken and to verify that it appears to be resolved.

> Versions of extensions should have no impact on ability to pull in artifacts
> ----------------------------------------------------------------------------
>
>                 Key: NIFI-222
>                 URL: https://issues.apache.org/jira/browse/NIFI-222
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Tools and Build
>            Reporter: Bryan Bende
>            Assignee: Joseph Witt
>              Labels: build, maven
>         Attachments: donothing-bundle.tar.gz
>
>
> Hi all,
> I'm trying to setup a Maven project for a custom nar and from looking at
> the other nars I created something like the following:
> 1) parent project with a pom that has two modules
> 2) a jar project where the main code lives, the pom for this project has a
> parent of the pom referenced in #1
> 3) a nar project that has a dependency on #2 and a parent of:
>  <parent>
>         <groupId>org.apache.nifi</groupId>
>         <artifactId>nar-bundle-parent</artifactId>
>         <version>0.0.1-SNAPSHOT</version>
>     </parent>
> Now all three of my poms had a version of 0.1-SNAPSHOT by default, so my
> nar project had something like this:
> <artifactId>example-nar</artifactId>
> <version>0.1-SNAPSHOT</version>
> <packaging>nar</packaging>
> When I ran mvn clean install from the root, the jar built fine, and when it
> hit the nar project it failed with this:
> The following artifacts could not be resolved:
> org.apache.nifi:nifi-api:jar:0.1-SNAPSHOT,
> org.apache.nifi:nifi-processor-utils:jar:0.1-SNAPSHOT
> For some reason it used the version of my nar to look for the Nifi
> artifacts, even though the dependencies I had declared in the jar project
> were:
> <dependency>
>             <groupId>org.apache.nifi</groupId>
>             <artifactId>nifi-api</artifactId>
>             <version>0.0.1-SNAPSHOT</version>
>             <scope>compile</scope>
>         </dependency>
>         <dependency>
>             <groupId>org.apache.nifi</groupId>
>             <artifactId>nifi-processor-utils</artifactId>
>             <version>0.0.1-SNAPSHOT</version>
>             <scope>compile</scope>
>         </dependency>
> Then I changed the version in my nar pom from 0.1-SNAPSHOT to
> 0.0.1-SNAPSHOT and the build works fine and I'm able to deploy the nar no
> problem.
> Is this the expected behavior, or did I set these projects up wrong?
> Thanks,
> Bryan
> ++++++
> As found here in maven docs:
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Aggregation
> The following quote is key:
> "One factor to note is that these variables are processed after inheritance as outlined above. This means that if a parent project uses a variable, then its definition in the child, not the parent, will be the one eventually used."



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