[
https://issues.apache.org/jira/browse/NIFI-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996781#comment-15996781
]
Bryan Bende commented on NIFI-3795:
-----------------------------------
[~jameswing] [~trixpan] [~joewitt]
I realized that as part of the component versioning work, we changed the
approach of populating the build info a little bit...
Previously the assembly was filtering the info into nifi.properties, but now we
populate the info in the MANIFEST of each NAR, and then NiFi use's the
framework NAR to display the info.
So I believe that we really don't need the buildnumber plugin and the no-git
profile in the assembly pom. We had already defined the buildnumber plugin in
nifi-nar-bundles/pom.xml so that each NAR got the info, so we can define the
no-git profile there.
Here is a commit that seems to work:
https://github.com/bbende/nifi/commit/cb576b725ea95add2525d575fc8db52c22dd2d9f
> nifi-assembly fails with "no formats specified" error
> -----------------------------------------------------
>
> Key: NIFI-3795
> URL: https://issues.apache.org/jira/browse/NIFI-3795
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Bryan Bende
> Assignee: James Wing
> Priority: Blocker
> Fix For: 1.2.0
>
>
> After staging the 1.2.0 RC1 artifacts, I then downloaded the source zip from
> the Nexus staging repo, unzipped it and ran "mvn clean install -DskipTests"
> to verify that it would build. I encountered the below error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5.2:single (make shared
> resource) on project nifi-assembly: No formats specified in the execution
> parameters or the assembly descriptor. -> [Help 1]
> After some debugging it was determined that one difference between this build
> and the previous build that staged the artifacts, is that this build was not
> within a git repo where as the other one was.
> After running git init, adding all files, and making a commit, then the build
> passed. Still unclear as to why being in a git repo matters here, although
> every NAR now tries to use the git info from the buildnumber plugin to filter
> into the MANIFEST files.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
