[
https://issues.apache.org/jira/browse/NIFI-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081190#comment-15081190
]
Joseph Witt commented on NIFI-1347:
-----------------------------------
before patch results:
[ERROR] Internal error: org.apache.maven.artifact.InvalidArtifactRTException:
For artifact {org.apache.nifi:nifi-riemann-processors:null:jar}: The version
cannot be empty. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be empty.
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.apache.nifi:nifi-riemann-processors:null:jar}: The version cannot be empty.
at
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:148)
at
org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123)
at
org.apache.maven.bridge.MavenRepositorySystem.XcreateArtifact(MavenRepositorySystem.java:695)
at
org.apache.maven.bridge.MavenRepositorySystem.XcreateDependencyArtifact(MavenRepositorySystem.java:613)
at
org.apache.maven.bridge.MavenRepositorySystem.createDependencyArtifact(MavenRepositorySystem.java:120)
at
org.apache.maven.project.DefaultProjectBuilder.initProject(DefaultProjectBuilder.java:808)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:617)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:405)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:663)
at
org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:654)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:243)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
... 11 more
> Use explicit version reference and fix dependency reference
> -----------------------------------------------------------
>
> Key: NIFI-1347
> URL: https://issues.apache.org/jira/browse/NIFI-1347
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Priority: Trivial
> Fix For: 0.5.0
>
> Attachments: 0001-NIFI-1347.patch
>
>
> The riemann bundle had the nifi-riemann-nar referencing a dependency using
> maven project version shortcut rather than explicit reference. We've
> abolished use of this because it has been observed to cause strange
> multi-module or release plugin related behavior and it offers no benefit.
> Versions are automatically managed during the release process and using
> version plugins as needed so not worth the hassle. Also, the dependency
> section of the bundle referenced the com.aphyr client which means each sub
> module automatically gets that dependency. Better to switch to
> dependencyManagement and then explicitly pull in the needed item on the
> appropriate artifact.
> Finally, adjusted the formatting to be more consistent with other modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
