That's what it was. Resolution was simple. ln -s ~/.m2 /root
Now I can build, update and restart Nifi service as root and the dependencies are found in both my local account and root. Not ideal, but what's a developer to do... Thanks for the assist. Rick -----Original Message----- From: Rick Braddy [mailto:[email protected]] Sent: Friday, September 04, 2015 1:03 PM To: [email protected] Subject: RE: POM dependency failures I may know what the problem is... I decided to run the build as 'root' user so my rebuild script would be able to copy over my NAR bundle and restart Nifi service... so it appears that since the Maven repository is associated with my local home directory, that may be why it's failing. I will create a link and see if that resolves the issue. Thanks for the pointer. Rick -----Original Message----- From: Rick Braddy [mailto:[email protected]] Sent: Friday, September 04, 2015 1:00 PM To: [email protected] Subject: RE: POM dependency failures Bryan, Yes. The 0.3.0-SNAPSHOT folders are there for each Nifi subsystem folder. root@rick-dev:~/.m2/repository/org/apache/nifi# ls nifi nifi-external nifi-mock nifi-processor-utils nifi-api nifi-framework-bundle nifi-nar-bundles nifi-provenance-repository-bundle nifi-commons nifi-maven-archetypes nifi-nar-maven-plugin ./nifi-provenance-repository-bundle/0.3.0-SNAPSHOT ./nifi-maven-archetypes/0.3.0-SNAPSHOT ./nifi-mock/0.3.0-SNAPSHOT ./nifi/0.3.0-SNAPSHOT ./nifi-external/0.3.0-SNAPSHOT ./nifi-processor-utils/0.3.0-SNAPSHOT ./nifi-nar-bundles/0.3.0-SNAPSHOT ./nifi-commons/0.3.0-SNAPSHOT ./nifi-api/0.3.0-SNAPSHOT ./nifi-framework-bundle/0.3.0-SNAPSHOT Rick -----Original Message----- From: Bryan Bende [mailto:[email protected]] Sent: Friday, September 04, 2015 12:54 PM To: [email protected] Subject: Re: POM dependency failures Rick, Can you check in your local Maven repository to see if the 0.3.0-SNAPSHOTs are in there? It is typically in HOME/.m2 As one example ~/.m2/repository/org/apache/nifi/nifi-api/ should have a sub-directory for 0.3.0-SNAPSHOT. -Bryan On Fri, Sep 4, 2015 at 2:50 PM, Rick Braddy <[email protected]> wrote: > Yes. I pulled source from Nifi on Github[1] and built it locally, > which seemed to work okay at first. > > Is there a better process to use? > > [1] https://github.com/apache/nifi > > > -----Original Message----- > From: Aldrin Piri [mailto:[email protected]] > Sent: Friday, September 04, 2015 12:46 PM > To: [email protected] > Subject: Re: POM dependency failures > > Rick, > > Did you do a build (mvn install) of the 0.3.0 repository on the same > machine you are doing this development on? We do not, as a project, > publish any snapshots and this would explain the issues in not being > able to locate the associate poms. > > On Fri, Sep 4, 2015 at 1:39 PM, Rick Braddy <[email protected]> wrote: > > > Hi, > > > > Does anyone know why these dependencies would suddenly start failing > > or how to go about resolving? > > > > [WARNING] The POM for org.apache.nifi:nifi-api:jar:0.3.0-SNAPSHOT is > > missing, no dependency information available [WARNING] The POM for > > org.apache.nifi:nifi-processor-utils:jar:0.3.0-SNAPSHOT is missing, > > no dependency information available [WARNING] The POM for > > org.apache.nifi:nifi-mock:jar:0.3.0-SNAPSHOT is missing, no > > dependency information available > > > > These errors occur during Maven build in a separate NAR bundle > > project created using Bryan's Customer Processor post here< > > http://bryanbende.com/development/2015/02/04/custom-processors-for-a > > pa > > che-nifi/> > > for developing custom processors. > > > > This Maven project had been building okay yesterday and just > > suddenly stopped working today (and I don't believe I changed any POM > > files)... > > > > Thanks > > Rick > > >
