nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <>
Subject [jira] [Created] (NIFI-222) Versions of extensions should have no impact on ability to pull in artifacts
Date Sat, 03 Jan 2015 05:40:34 GMT
Joseph Witt created NIFI-222:

             Summary: Versions of extensions should have no impact on ability to pull in artifacts
                 Key: NIFI-222
             Project: Apache NiFi
          Issue Type: Bug
          Components: Tools and Build
            Reporter: Bryan Bende
            Assignee: Joseph Witt

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:

Now all three of my poms had a version of 0.1-SNAPSHOT by default, so my
nar project had something like this:


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:

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


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

Is this the expected behavior, or did I set these projects up wrong?



As found here in maven docs:

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

View raw message