nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Psaltis <psaltis.and...@gmail.com>
Subject Re: Build error for the custom processor against 0.7.0-SNAPSHOT
Date Tue, 10 May 2016 19:04:01 GMT
Hi Kumiko,
I am not sure of the exact maven command you were using to generate the
archetype.  However when looking at the Maven repository here (
https://repo1.maven.org/maven2/org/apache/nifi/nifi-maven-archetypes/) I do
not see the 0.7.0-SNAPSHOT.  I may be mistaken, but I think the most recent
version is actually 0.6.1. Did you by chance build the maven archetypes
locally?


Thanks,
Andrew

On Tue, May 10, 2016 at 2:48 PM, Kumiko Yada <Kumiko.Yada@ds-iq.com> wrote:

> Hello,
>
>
>
> I’m getting the following build error against 0.7.0-SNAPSHOT.  I also
> tried to create a new custom processor again for 0.7.0-SNAPSHOT and getting
> the same error.  Is this a known issue?
>
>
>
> Build error:
>
> [INFO] Scanning for projects...
>
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
>
> [FATAL] Non-resolvable parent POM for xxxx:xxxxprocessors:1.0: Could not
> find artifact org.apache.nifi:nifi-nar-bundles:pom:0.7.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 19, column 13
>
> @
>
>
>
> Creating new processor error:
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 15.235 s
>
> [INFO] Finished at: 2016-05-10T11:42:03-07:00
>
> [INFO] Final Memory: 13M/219M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli)
> on project standalone-pom: The desired archetype does not exist
> (org.apache.nifi:nifi-processor-bundle-archetype:0.7.0-SNAPSHOT) -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>
>
> Thanks
>
> Kumiko
>



-- 
Thanks,
Andrew

Subscribe to my book: Streaming Data <http://manning.com/psaltis>
<https://www.linkedin.com/pub/andrew-psaltis/1/17b/306>
twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata>

Mime
View raw message